Bump the combined-dependencies group across 1 directory with 3 updates #1507

dependabot · 2024-08-20T09:52:08Z

Bumps the combined-dependencies group with 3 updates in the / directory: @sentry/browser, esbuild and govuk-frontend.

Updates @sentry/browser from 8.22.0 to 8.26.0

Release notes

Sourced from @sentry/browser's releases.

8.26.0

Important Changes
feat(node): Add fsInstrumentation (#13291)

This release adds fsIntegration, an integration that instruments the fs API to the Sentry Node SDK. The integration creates spans with naming patterns of fs.readFile, fs.unlink, and so on.

This integration is not enabled by default and needs to be registered in your Sentry.init call. You can configure via options whether to include path arguments or error messages as span attributes when an fs call fails:
Sentry.init({
  integrations: [
    Sentry.fsIntegration({
      recordFilePaths: true,
      recordErrorMessagesAsSpanAttributes: true,
    }),
  ],
});
WARNING: This integration may add significant overhead to your application. Especially in scenarios with a lot of file I/O, like for example when running a framework dev server, including this integration can massively slow down your application.
Other Changes

feat(browser): Add spotlightBrowser integration (#13263)

feat(browser): Allow sentry in safari extension background page (#13209)

feat(browser): Send CLS as standalone span (experimental) (#13056)

feat(core): Add OpenTelemetry-specific getTraceData implementation (#13281)

feat(nextjs): Always add browserTracingIntegration (#13324)

feat(nextjs): Always transmit trace data to the client (#13337)

feat(nextjs): export SentryBuildOptions (#13296)

feat(nextjs): Update experimental_captureRequestError to reflect RequestInfo.path change in Next.js canary (#13344)

feat(nuxt): Always add tracing meta tags (#13273)

feat(nuxt): Set transaction name for server error (#13292)

feat(replay): Add a replay-specific logger (#13256)

feat(sveltekit): Add bundle size optimizations to plugin options (#13318)

feat(sveltekit): Always add browserTracingIntegration (#13322)

feat(tracing): Make long animation frames opt-out (#13255)

fix(astro): Correctly extract request data (#13315)

fix(astro): Only track access request headers in dynamic page requests (#13306)

fix(nuxt): Add import line for disabled autoImport (#13342)

fix(nuxt): Add vue to excludeEsmLoaderHooks array (#13346)

fix(opentelemetry): Do not overwrite http span name if kind is internal (#13282)

fix(remix): Ensure origin is correctly set for remix server spans (#13305)

... (truncated)

Changelog

Sourced from @sentry/browser's changelog.

8.26.0

Important Changes
feat(node): Add fsInstrumentation (#13291)

This release adds fsIntegration, an integration that instruments the fs API to the Sentry Node SDK. The integration creates spans with naming patterns of fs.readFile, fs.unlink, and so on.

This integration is not enabled by default and needs to be registered in your Sentry.init call. You can configure via options whether to include path arguments or error messages as span attributes when an fs call fails:
Sentry.init({
  integrations: [
    Sentry.fsIntegration({
      recordFilePaths: true,
      recordErrorMessagesAsSpanAttributes: true,
    }),
  ],
});
WARNING: This integration may add significant overhead to your application. Especially in scenarios with a lot of file I/O, like for example when running a framework dev server, including this integration can massively slow down your application.
Other Changes

feat(browser): Add spotlightBrowser integration (#13263)

feat(browser): Allow sentry in safari extension background page (#13209)

feat(browser): Send CLS as standalone span (experimental) (#13056)

feat(core): Add OpenTelemetry-specific getTraceData implementation (#13281)

feat(nextjs): Always add browserTracingIntegration (#13324)

feat(nextjs): Always transmit trace data to the client (#13337)

feat(nextjs): export SentryBuildOptions (#13296)

feat(nextjs): Update experimental_captureRequestError to reflect RequestInfo.path change in Next.js canary (#13344)

feat(nuxt): Always add tracing meta tags (#13273)

feat(nuxt): Set transaction name for server error (#13292)

feat(replay): Add a replay-specific logger (#13256)

feat(sveltekit): Add bundle size optimizations to plugin options (#13318)

feat(sveltekit): Always add browserTracingIntegration (#13322)

feat(tracing): Make long animation frames opt-out (#13255)

fix(astro): Correctly extract request data (#13315)

fix(astro): Only track access request headers in dynamic page requests (#13306)

fix(nuxt): Add import line for disabled autoImport (#13342)

fix(nuxt): Add vue to excludeEsmLoaderHooks array (#13346)

fix(opentelemetry): Do not overwrite http span name if kind is internal (#13282)

... (truncated)

Commits

bff9dfd release: 8.26.0
93fe406 Merge pull request #13351 from getsentry/prepare-release/8.26.0
2d4e4f5 meta: Update Changelog for 8.26.0
3fc12c6 fix(ci): Fix incorrect changed_any_code check in job_build (#13353)
fd49d0b fix(nuxt): Add vue to excludeEsmLoaderHooks array (#13346)
6c0f01a fix(ci): Bring back job skipping for PRs without code changes (#13340)
334f869 docs(vercel-edge): Update @sentry/vercel-edge readme to remove alpha status...
043ae7e feat(nextjs): Always transmit trace data to the client (#13337)
3871892 feat(nextjs): Update experimental_captureRequestError to reflect `RequestIn...
e623782 fix(nuxt): Add import line for disabled autoImport (#13342)
Additional commits viewable in compare view

Updates esbuild from 0.23.0 to 0.23.1

Release notes

Sourced from esbuild's releases.

v0.23.1
Allow using the node: import prefix with es* targets (#3821)

The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:
// Original code
import fs from 'node:fs'
fs.open
// Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "fs";
fs.open;
// New output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "node:fs";
fs.open;
Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

Fix incorrect location of certain error messages (#3845)

This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

Print comments before case clauses in switch statements (#3838)

With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

Fix a memory leak with pluginData (#3825)

With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

Changelog

Sourced from esbuild's changelog.

0.23.1
Allow using the node: import prefix with es* targets (#3821)

The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:
// Original code
import fs from 'node:fs'
fs.open
// Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "fs";
fs.open;
// New output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "node:fs";
fs.open;
Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

Fix incorrect location of certain error messages (#3845)

This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

Print comments before case clauses in switch statements (#3838)

With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

Fix a memory leak with pluginData (#3825)

With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

Commits

3327274 publish 0.23.1 to npm
38e22ed add a warning/debug log message for #3867
a15bb51 fix #3825: memory leak of pluginData values
f6e6481 fix #3838: print comments before case clauses
9c13ae1 fix #3853: update go 1.22.4 => 1.22.5
78f89e4 fix #3845: some incorrect error message locations
892d2a7 fix #3834: cli sometimes panics with --analyze
360d472 fix a typo in the release notes
e3f4e2d fix #3821: allow node: prefix with es* targets
See full diff in compare view

Updates govuk-frontend from 5.4.1 to 5.5.0

Release notes

Sourced from govuk-frontend's releases.

GOV.UK Frontend v5.5.0

This release includes an updated list of organisations and brand colours. We’ve also added a new feature to stop long words from ‘breaking out’ of components.

To install this version with npm, run npm install [email protected]. You can also find more information about how to stay up to date in our documentation.

New features

We've updated the list of organisations and brand colours included in Frontend

We've overhauled the list of organisations and organisation brand colours that are shipped with GOV.UK Frontend.

The previous list was outdated and had not kept up with changes to the machinery of government. We’ve updated the list to:

add all current government departments and their brand colours

add variants of brand colours that meet a 4.5:1 contrast ratio against white, where required

provide warnings if defunct organisations are still being referenced in your Sass code

To enable these changes, set the feature flag variable $govuk-new-organisation-colours to true before you import GOV.UK Frontend in your Sass files:
// application.scss
$govuk-new-organisation-colours: true;
@import "govuk-frontend/all";
You can also silence warnings about defunct organisations by adding organisation-colours to the $govuk-suppressed-warnings setting.

We introduced this change in [pull request #3407: Update organisation colours](alphagov/govuk-frontend#3407).

Stop long words breaking out of components with govuk-!-text-break-word

We've added a new override class to help display long words with no obvious break points when the space is too narrow to display them on one line. An example of a long word might be an email address entered by a user.

Wrapping the content with the govuk-!-text-break-word class forces words that are too long for the parent element to break onto a new line.
A confirmation email will be sent to <span class="govuk-!-text-break-word">arthur_phillip_dent.42@peoplepersonalitydivision.siriuscyberneticscorporation.corp</span>.
Sass users can also use the govuk-text-break-word mixin.

We introduced this change in [pull request #5159: Add break-word typography helper](alphagov/govuk-frontend#5159).

Recommended changes

Update the $websafe parameter on the govuk-organisation-colour function

The govuk-organisation-colour Sass function's $websafe parameter has been renamed to $contrast-safe.

This is to more accurately describe the functionality of the parameter.

... (truncated)

Changelog

Sourced from govuk-frontend's changelog.

v5.5.0 (Feature release)

To install this version with npm, run npm install [email protected]. You can also find more information about how to stay up to date in our documentation.

New features

We've updated the list of organisations and brand colours included in Frontend

We've overhauled the list of organisations and organisation brand colours that are shipped with GOV.UK Frontend.

The previous list was outdated and had not kept up with changes to the machinery of government. We’ve updated the list to:

add all current government departments and their brand colours

add variants of brand colours that meet a 4.5:1 contrast ratio against white, where required

provide warnings if defunct organisations are still being referenced in your Sass code

To enable these changes, set the feature flag variable $govuk-new-organisation-colours to true before you import GOV.UK Frontend in your Sass files:
// application.scss
$govuk-new-organisation-colours: true;
@import "govuk-frontend/all";
You can also silence warnings about defunct organisations by adding organisation-colours to the $govuk-suppressed-warnings setting.

We introduced this change in [pull request #3407: Update organisation colours](alphagov/govuk-frontend#3407).

Stop long words breaking out of components with govuk-!-text-break-word

We've added a new override class to help display long words with no obvious break points when the space is too narrow to display them on one line. An example of a long word might be an email address entered by a user.

Wrapping the content with the govuk-!-text-break-word class forces words that are too long for the parent element to break onto a new line.
A confirmation email will be sent to <span class="govuk-!-text-break-word">arthur_phillip_dent.42@peoplepersonalitydivision.siriuscyberneticscorporation.corp</span>.
Sass users can also use the govuk-text-break-word mixin.

We introduced this change in [pull request #5159: Add break-word typography helper](alphagov/govuk-frontend#5159).

Recommended changes

Update the $websafe parameter on the govuk-organisation-colour function

The govuk-organisation-colour Sass function's $websafe parameter has been renamed to $contrast-safe.

This is to more accurately describe the functionality of the parameter.

... (truncated)

Commits

2101cd5 Release v5.5.0
7e5ec60 Merge pull request #5203 from alphagov/add-cycle-brief-issue-template
e858bd9 Merge pull request #3407 from alphagov/update-organisation-colours
4556a88 Merge pull request #5197 from alphagov/dependabot/npm_and_yarn/test-59336de5a9
2263449 Bump puppeteer from 22.14.0 to 22.15.0 in the test group
1acd94d Clean up various parts
85f5de1 Merge pull request #5191 from alphagov/fix-back-link-falsy-values
581bfd2 Add issue template for cycle briefs
6d99967 Add CHANGELOG entry
5b2cd64 Fix rendering of Back link's href and text for falsy values
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

starswan · 2024-08-20T10:03:44Z

@dependabot rebase

Bumps the combined-dependencies group with 3 updates in the / directory: [@sentry/browser](https://github.com/getsentry/sentry-javascript), [esbuild](https://github.com/evanw/esbuild) and [govuk-frontend](https://github.com/alphagov/govuk-frontend). Updates `@sentry/browser` from 8.22.0 to 8.26.0 - [Release notes](https://github.com/getsentry/sentry-javascript/releases) - [Changelog](https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md) - [Commits](getsentry/sentry-javascript@8.22.0...8.26.0) Updates `esbuild` from 0.23.0 to 0.23.1 - [Release notes](https://github.com/evanw/esbuild/releases) - [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md) - [Commits](evanw/esbuild@v0.23.0...v0.23.1) Updates `govuk-frontend` from 5.4.1 to 5.5.0 - [Release notes](https://github.com/alphagov/govuk-frontend/releases) - [Changelog](https://github.com/alphagov/govuk-frontend/blob/main/CHANGELOG.md) - [Commits](alphagov/govuk-frontend@v5.4.1...v5.5.0) --- updated-dependencies: - dependency-name: "@sentry/browser" dependency-type: direct:production update-type: version-update:semver-minor dependency-group: combined-dependencies - dependency-name: esbuild dependency-type: direct:production update-type: version-update:semver-patch dependency-group: combined-dependencies - dependency-name: govuk-frontend dependency-type: direct:production update-type: version-update:semver-minor dependency-group: combined-dependencies ... Signed-off-by: dependabot[bot] <[email protected]>

dependabot bot requested a review from a team as a code owner August 20, 2024 09:52

dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Aug 20, 2024

starswan approved these changes Aug 20, 2024

View reviewed changes

dependabot bot force-pushed the dependabot/npm_and_yarn/combined-dependencies-eb7370c2a7 branch from 92c9878 to 282f1b2 Compare August 20, 2024 10:05

starswan merged commit 28021c3 into main Aug 20, 2024
11 checks passed

starswan deleted the dependabot/npm_and_yarn/combined-dependencies-eb7370c2a7 branch August 20, 2024 10:13

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bump the combined-dependencies group across 1 directory with 3 updates #1507

Bump the combined-dependencies group across 1 directory with 3 updates #1507

dependabot bot commented on behalf of github Aug 20, 2024 •

edited

Loading

starswan commented Aug 20, 2024

Bump the combined-dependencies group across 1 directory with 3 updates #1507

Bump the combined-dependencies group across 1 directory with 3 updates #1507

Conversation

dependabot bot commented on behalf of github Aug 20, 2024 • edited Loading

8.26.0

Important Changes

Other Changes

8.26.0

Important Changes

Other Changes

v0.23.1

0.23.1

GOV.UK Frontend v5.5.0

New features

We've updated the list of organisations and brand colours included in Frontend

Stop long words breaking out of components with govuk-!-text-break-word

Recommended changes

Update the $websafe parameter on the govuk-organisation-colour function

v5.5.0 (Feature release)

New features

We've updated the list of organisations and brand colours included in Frontend

Stop long words breaking out of components with govuk-!-text-break-word

Recommended changes

Update the $websafe parameter on the govuk-organisation-colour function

starswan commented Aug 20, 2024

dependabot bot commented on behalf of github Aug 20, 2024 •

edited

Loading

Stop long words breaking out of components with `govuk-!-text-break-word`

Update the `$websafe` parameter on the `govuk-organisation-colour` function

Stop long words breaking out of components with `govuk-!-text-break-word`

Update the `$websafe` parameter on the `govuk-organisation-colour` function