build(dev-deps): bump the all-non-major-dependencies group in /e2e/release/sample with 5 updates

[dependabot]

Bumps the all-non-major-dependencies group in /e2e/release/sample with 5 updates:

Package	From	To
@sentry/react	8.40.0	8.41.0
@tsconfig/vite-react	3.0.2	3.4.0
@types/node	22.9.3	22.10.1
@vitejs/plugin-react	4.3.3	4.3.4
prettier	3.3.3	3.4.1

Updates @sentry/react from 8.40.0 to 8.41.0

Release notes

Sourced from @​sentry/react's releases.

8.41.0

Important Changes

• meta(nuxt): Require minimum Nuxt v3.7.0 (#14473)

  We formalized that the Nuxt SDK is at minimum compatible with Nuxt version 3.7.0 and above. Additionally, the SDK requires the implicit nitropack dependency to satisfy version ^2.10.0 and ofetch to satisfy ^1.4.0. It is recommended to check your lock-files and manually upgrade these dependencies if they don't match the version ranges.

Deprecations

We are deprecating a few APIs which will be removed in the next major.

The following deprecations will potentially affect you:

• feat(core): Update & deprecate undefined option handling (#14450)

  In the next major version we will change how passing undefined to tracesSampleRate / tracesSampler / enableTracing will behave.

  Currently, doing the following:

  Sentry.init({
    tracesSampleRate: undefined,
  });

  Will result in tracing being enabled (although no spans will be generated) because the tracesSampleRate key is present in the options object. In the next major version, this behavior will be changed so that passing undefined (or rather having a tracesSampleRate key) will result in tracing being disabled, the same as not passing the option at all. If you are currently relying on undefined being passed, and and thus have tracing enabled, it is recommended to update your config to set e.g. tracesSampleRate: 0 instead, which will also enable tracing in v9.

  The same applies to tracesSampler and enableTracing.

• feat(core): Log warnings when returning null in beforeSendSpan (#14433)

  Currently, the beforeSendSpan option in Sentry.init() allows you to drop individual spans from a trace by returning null from the hook. Since this API lends itself to creating "gaps" inside traces, we decided to change how this API will work in the next major version.

  With the next major version the beforeSendSpan API can only be used to mutate spans, but no longer to drop them. With this release the SDK will warn you if you are using this API to drop spans. Instead, it is recommended to configure instrumentation (i.e. integrations) directly to control what spans are created.

  Additionally, with the next major version, root spans will also be passed to beforeSendSpan.

• feat(utils): Deprecate @sentry/utils (#14431)

  With the next major version the @sentry/utils package will be merged into the @sentry/core package. It is therefore no longer recommended to use the @sentry/utils package.

• feat(vue): Deprecate configuring Vue tracing options anywhere else other than through the vueIntegration's tracingOptions option (#14385)

... (truncated)

Changelog

Sourced from @​sentry/react's changelog.

8.41.0

Important Changes

• meta(nuxt): Require minimum Nuxt v3.7.0 (#14473)

  We formalized that the Nuxt SDK is at minimum compatible with Nuxt version 3.7.0 and above. Additionally, the SDK requires the implicit nitropack dependency to satisfy version ^2.10.0 and ofetch to satisfy ^1.4.0. It is recommended to check your lock-files and manually upgrade these dependencies if they don't match the version ranges.

Deprecations

We are deprecating a few APIs which will be removed in the next major.

The following deprecations will potentially affect you:

• feat(core): Update & deprecate undefined option handling (#14450)

  In the next major version we will change how passing undefined to tracesSampleRate / tracesSampler / enableTracing will behave.

  Currently, doing the following:

  Sentry.init({
    tracesSampleRate: undefined,
  });

  Will result in tracing being enabled (although no spans will be generated) because the tracesSampleRate key is present in the options object. In the next major version, this behavior will be changed so that passing undefined (or rather having a tracesSampleRate key) will result in tracing being disabled, the same as not passing the option at all. If you are currently relying on undefined being passed, and and thus have tracing enabled, it is recommended to update your config to set e.g. tracesSampleRate: 0 instead, which will also enable tracing in v9.

  The same applies to tracesSampler and enableTracing.

• feat(core): Log warnings when returning null in beforeSendSpan (#14433)

  Currently, the beforeSendSpan option in Sentry.init() allows you to drop individual spans from a trace by returning null from the hook. Since this API lends itself to creating "gaps" inside traces, we decided to change how this API will work in the next major version.

  With the next major version the beforeSendSpan API can only be used to mutate spans, but no longer to drop them. With this release the SDK will warn you if you are using this API to drop spans. Instead, it is recommended to configure instrumentation (i.e. integrations) directly to control what spans are created.

  Additionally, with the next major version, root spans will also be passed to beforeSendSpan.

• feat(utils): Deprecate @sentry/utils (#14431)

  With the next major version the @sentry/utils package will be merged into the @sentry/core package. It is therefore no longer recommended to use the @sentry/utils package.

... (truncated)

Commits

• df843cc release: 8.41.0
• 470d4ec Merge pull request #14502 from getsentry/prepare-release/8.41.0
• f7289c4 meta(changelog): Update changelog for 8.41.0
• a4138e9 perf(opentelemetry): Bucket spans for cleanup (#14154)
• 3e7969f feat: Deprecate registerEsmLoaderHooks.include and `registerEsmLoaderHooks....
• 1e0cb04 ref(core): Do not check baggage validity (#14479)
• de65590 feat(core): Further optimize debug ID parsing (#14365)
• 09a31d1 feat(node): Add openTelemetryInstrumentations option (#14484)
• 23e3783 meta(nuxt): Require minimum Nuxt v3.7.0 (#14473)
• 973ef9c chore: Add GHSA entry for nuxt e2e test (#14490)
• Additional commits viewable in compare view

Updates @tsconfig/vite-react from 3.0.2 to 3.4.0

Commits

• See full diff in compare view

Updates @types/node from 22.9.3 to 22.10.1

Commits

• See full diff in compare view

Updates @vitejs/plugin-react from 4.3.3 to 4.3.4

Release notes

Sourced from @​vitejs/plugin-react's releases.

v4.3.4

Add Vite 6 to peerDependencies range

Vite 6 is highly backward compatible, not much to add!

Force Babel to output spec compliant import attributes #386

The default was an old spec (with type: "json"). We now enforce spec compliant (with { type: "json" })

Changelog

Sourced from @​vitejs/plugin-react's changelog.

4.3.4 (2024-11-26)

Add Vite 6 to peerDependencies range

Vite 6 is highly backward compatible, not much to add!

Force Babel to output spec compliant import attributes #386

The default was an old spec (with type: "json"). We now enforce spec compliant (with { type: "json" })

Commits

• 2e368a6 release: [email protected]
• bde1ad6 feat: add Vite 6 to peerDependencies range (#390)
• 45a727c fix(deps): update all non-major dependencies (#373)
• 5d2b6c6 fix: force non-legacy import attributes babel output (#386)
• See full diff in compare view

Updates prettier from 3.3.3 to 3.4.1

Release notes

Sourced from prettier's releases.

3.4.1

🔗 Changelog

3.4.0

diff

🔗 Release note

Changelog

Sourced from prettier's changelog.

3.4.1

diff

Remove unnecessary parentheses around assignment in v-on (#16887 by @​fisker)

<!-- Input -->
\<template>
  <button @click="foo += 2">Click</button>
</template>
<!-- Prettier 3.4.0 -->
&lt;template>
<button @​click="(foo += 2)">Click</button>
</template>
<!-- Prettier 3.4.1 -->
&lt;template>
<button @​click="foo += 2">Click</button>
</template>

3.4.0

diff

🔗 Release Notes

Commits

• 37fd177 Release 3.4.1
• 1fb6297 Update ts-api-utils to v1.4.2 (#16888)
• f6fccad Remove unnecessary parentheses around assignment in v-on (#16887)
• 5fef089 Minor improvements in v3.4.0 blog post (#16886)
• 3542f13 3.4 release blog (#16851)
• f53791a Clean changelog_unreleased
• 2b41c93 Bump Prettier dependency to 3.4.0
• 10baab2 Update dependents count
• 7999e10 Release 3.4.0
• 2262d1e chore(config): migrate renovate config (#16884)
• 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

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dependabot]

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