Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump @sentry/vue from 7.110.1 to 8.4.0 #1727

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 27, 2024

Bumps @sentry/vue from 7.110.1 to 8.4.0.

Release notes

Sourced from @​sentry/vue's releases.

8.4.0

Important Changes

  • feat(nextjs): Trace pageloads in App Router (#12157)

If you are using Next.js version 14.3.0-canary.64 or above, the Sentry Next.js SDK will now trace clientside pageloads with React Server Components. This means, that client-side errors like Error: An error occurred in the Server Components render., which previously didn't give you much information on how that error was caused, can now be traced back to a specific error in a server component.

  • feat(angular): Add Support for Angular 18 (#12183)

This release guarantees support for Angular 18 with @sentry/angular.

Other Changes

  • feat(deps): Bump @​opentelemetry/instrumentation-aws-lambda from 0.41.0 to 0.41.1 (#12078)
  • fix(metrics): Ensure string values are interpreted for metrics (#12165)

Bundle size 📦

Path Size
@​sentry/browser 21.74 KB
@​sentry/browser (incl. Tracing) 32.88 KB
@​sentry/browser (incl. Tracing, Replay) 68.25 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags 61.66 KB
@​sentry/browser (incl. Tracing, Replay with Canvas) 72.28 KB
@​sentry/browser (incl. Tracing, Replay, Feedback) 84.33 KB
@​sentry/browser (incl. Feedback) 37.75 KB
@​sentry/browser (incl. sendFeedback) 26.31 KB
@​sentry/browser (incl. FeedbackAsync) 30.73 KB
@​sentry/react 24.43 KB
@​sentry/react (incl. Tracing) 35.88 KB
@​sentry/vue 25.68 KB
@​sentry/vue (incl. Tracing) 34.7 KB
@​sentry/svelte 21.88 KB
CDN Bundle 24.28 KB
CDN Bundle (incl. Tracing) 34.35 KB
CDN Bundle (incl. Tracing, Replay) 68.04 KB
CDN Bundle (incl. Tracing, Replay, Feedback) 73.03 KB
CDN Bundle - uncompressed 71.46 KB
CDN Bundle (incl. Tracing) - uncompressed 101.87 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed 211.5 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 223.85 KB
@​sentry/nextjs (client) 35.14 KB
@​sentry/sveltekit (client) 33.48 KB
@​sentry/node 114.31 KB
@​sentry/aws-serverless 103.2 KB

... (truncated)

Changelog

Sourced from @​sentry/vue's changelog.

8.4.0

Important Changes

  • feat(nextjs): Trace pageloads in App Router (#12157)

If you are using Next.js version 14.3.0-canary.64 or above, the Sentry Next.js SDK will now trace clientside pageloads with React Server Components. This means, that client-side errors like Error: An error occurred in the Server Components render., which previously didn't give you much information on how that error was caused, can now be traced back to a specific error in a server component.

  • feat(angular): Add Support for Angular 18 (#12183)

This release guarantees support for Angular 18 with @sentry/angular.

Other Changes

  • feat(deps): Bump @​opentelemetry/instrumentation-aws-lambda from 0.41.0 to 0.41.1 (#12078)
  • fix(metrics): Ensure string values are interpreted for metrics (#12165)

8.3.0

Important Changes

  • Better Node Framework Span Data

This release improves data quality of spans emitted by Express, Fastify, Connect, Koa, Nest.js and Hapi.

  • feat(node): Ensure connect spans have better data (#12130)

  • feat(node): Ensure express spans have better data (#12107)

  • feat(node): Ensure fastify spans have better data (#12106)

  • feat(node): Ensure hapi spans have better data (#12140)

  • feat(node): Ensure koa spans have better data (#12108)

  • feat(node): Ensure Nest.js spans have better data (#12139)

  • feat(deps): Bump @​opentelemetry/instrumentation-express from 0.38.0 to 0.39.0 (#12079)

  • feat(node): No-code init via --import=@sentry/node/init (#11999)

When using Sentry in ESM mode, you can now use Sentry without manually calling init like this:

 SENTRY_DSN=https://examplePublicKey@o0.ingest.sentry.io/0 node --import=@sentry/node/init app.mjs

When using CommonJS, you can do:

 SENTRY_DSN=https://examplePublicKey@o0.ingest.sentry.io/0 node --require=@sentry/node/init app.js

... (truncated)

Commits
  • fa14035 release: 8.4.0
  • 5e5c933 Merge pull request #12190 from getsentry/prepare-release/8.4.0
  • b203c2b meta(changelog): Update changelog for 8.4.0
  • d5a332c feat(nextjs): Trace pageloads in App Router (#12157)
  • 4caf92c ci(e2e): Use react beta for Next.js canary tests (#12186)
  • a0332fa feat(deps): Bump @​opentelemetry/instrumentation-aws-lambda from 0.41.0 to 0.4...
  • 6c28d4b feat(angular): Add Support for Angular 18 (#12183)
  • a45bdd1 fix(metrics): Ensure string values are interpreted for metrics (#12165)
  • 6254629 Merge pull request #12173 from getsentry/master
  • 37d09ca Merge branch 'release/8.3.0'
  • Additional commits viewable in compare view

Dependabot compatibility score

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [@sentry/vue](https://github.com/getsentry/sentry-javascript) from 7.110.1 to 8.4.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@7.110.1...8.4.0)

---
updated-dependencies:
- dependency-name: "@sentry/vue"
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot requested a review from skyYaga as a code owner May 27, 2024 12:09
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label May 27, 2024
Copy link

sonarcloud bot commented May 27, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

Copy link
Contributor Author

dependabot bot commented on behalf of github May 29, 2024

Superseded by #1728.

@dependabot dependabot bot closed this May 29, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/sentry/vue-8.4.0 branch May 29, 2024 12:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants