Bump the combined-dependencies group with 2 updates

[dependabot]

Bumps the combined-dependencies group with 2 updates: @sentry/browser and govuk-frontend.

Updates @sentry/browser from 8.26.0 to 8.27.0

Release notes

Sourced from @​sentry/browser's releases.

8.27.0

Important Changes

• fix(nestjs): Exception filters in main app module are not being executed (#13278)

  With this release nestjs error monitoring is no longer automatically set up after adding the SentryModule to your application, which led to issues in certain scenarios. You will now have to either add the SentryGlobalFilter to your main module providers or decorate the catch() method in your existing global exception filters with the newly released @WithSentry() decorator. See the docs for more details.

Other Changes

• feat: Add options for passing nonces to feedback integration (#13347)
• feat: Add support for SENTRY_SPOTLIGHT env var in Node (#13325)
• feat(deps): bump @​prisma/instrumentation from 5.17.0 to 5.18.0 (#13327)
• feat(feedback): Improve error message for 403 errors (#13441)
• fix(deno): Don't rely on Deno.permissions.querySync (#13378)
• fix(replay): Ensure we publish replay CDN bundles (#13437)

Work in this release was contributed by @​charpeni. Thank you for your contribution!

Changelog

Sourced from @​sentry/browser's changelog.

8.27.0

Important Changes

• fix(nestjs): Exception filters in main app module are not being executed (#13278)

  With this release nestjs error monitoring is no longer automatically set up after adding the SentryModule to your application, which led to issues in certain scenarios. You will now have to either add the SentryGlobalFilter to your main module providers or decorate the catch() method in your existing global exception filters with the newly released @WithSentry() decorator. See the docs for more details.

Other Changes

• feat: Add options for passing nonces to feedback integration (#13347)
• feat: Add support for SENTRY_SPOTLIGHT env var in Node (#13325)
• feat(deps): bump @​prisma/instrumentation from 5.17.0 to 5.18.0 (#13327)
• feat(feedback): Improve error message for 403 errors (#13441)
• fix(deno): Don't rely on Deno.permissions.querySync (#13378)
• fix(replay): Ensure we publish replay CDN bundles (#13437)

Work in this release was contributed by @​charpeni. Thank you for your contribution!

Commits

• 66a6316 release: 8.27.0
• 706ebd3 Merge pull request #13474 from getsentry/prepare-release/8.27.0
• b0180be Merge branch 'master' into prepare-release/8.27.0
• 205f127 meta: Update CHANGELOG for 8.27.0
• ea847d1 ci: Don't fail profiling bindings job on cache miss (#13464)
• 5b9d3bb ci: Always run build on develop branch (#13404)
• 195482c ci: Stabilize CI dependency cache key (#13401)
• 6cb6999 test: Fix flaky csp test (#13376)
• 80a116b fix(replay): Ensure we publish replay CDN bundles (#13437)
• e6861cf feat(feedback): Improve error message for 403 errors (#13441)
• Additional commits viewable in compare view

Updates govuk-frontend from 5.5.0 to 5.6.0

Release notes

Sourced from govuk-frontend's releases.

GOV.UK Frontend v5.6.0

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

Make it easier to navigate complex services with the Service navigation component

We've added a new Service navigation component to help users to navigate services with multiple top-level sections. This replaces the navigation functions of the Header component, which will be deprecated in a future release of GOV.UK Frontend.

This component includes some features we consider experimental. We intend to iterate these features in response to user feedback. These are:

• moving the service name from the Header to the Service navigation
• providing slots for injecting custom HTML into specified locations within the component

We introduced this change in [pull request #5206: Service navigation component](alphagov/govuk-frontend#5206).

Changelog

Sourced from govuk-frontend's changelog.

v5.6.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

Make it easier to navigate complex services with the Service navigation component

We've added a new Service navigation component to help users to navigate services with multiple top-level sections. This replaces the navigation functions of the Header component, which will be deprecated in a future release of GOV.UK Frontend.

This component includes some features we consider experimental. We intend to iterate these features in response to user feedback. These are:

• moving the service name from the Header to the Service navigation
• providing slots for injecting custom HTML into specified locations within the component

We introduced this change in [pull request #5206: Service navigation component](alphagov/govuk-frontend#5206).

Commits

• a5a50ea Merge pull request #5274 from alphagov/release-5.6.0
• 8dcbb4e Release v5.6.0
• dd473a3 Merge pull request #5206 from alphagov/service-navigation-component
• 414298b Update changelog
• 37877d0 Add service navigation component
• 3362ddf Merge pull request #5269 from alphagov/dependabot/npm_and_yarn/micromatch-4.0.8
• 79fd793 Bump micromatch from 4.0.7 to 4.0.8
• 8acdba6 Merge pull request #5266 from alphagov/dependabot/npm_and_yarn/caniuse-lite-1...
• f7ac619 Merge pull request #5265 from alphagov/dependabot/npm_and_yarn/testing-librar...
• e473fa4 Merge pull request #5264 from alphagov/dependabot/npm_and_yarn/marked-14.1.0
• 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

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.