fix(deps): update sentry-javascript monorepo to v7.12.0 #2307

Merged
konrad merged 1 commits from renovate/sentry-javascript-monorepo into main 2022-09-02 06:45:30 +00:00
Member

This PR contains the following updates:

Package Type Update Change
@sentry/tracing dependencies minor 7.11.1 -> 7.12.0
@sentry/vue dependencies minor 7.11.1 -> 7.12.0

Release Notes

getsentry/sentry-javascript

v7.12.0

Compare Source

This release adds an environment check in @sentry/nextjs for Vercel deployments (using the VERCEL_ENV env variable), and only enables SentryWebpackPlugin if the environment is production. To override this, setting disableClientWebpackPlugin or disableServerWebpackPlugin to false now takes precedence over other checks, rather than being a no-op. Note: Overriding this is not recommended! It can increase build time and clog Release Health data in Sentry with inaccurate noise.

  • feat(nextjs): Create transactions in getInitialProps and getServerSideProps (#​5593)
  • feat(nextjs): Instrument server-side getInitialProps of _app, _document and _error (#​5604)
  • feat(node): Populate event.contexts for Node.js (#​5512)
  • feat(svelte): Add Component Tracking (#​5612)
  • fix(browser): use valid urls in Request checks (#​5630)
  • fix(integrations): Don't add empty stack trace in RewriteFrames (#​5625)
  • fix(nextjs): Start navigation transactions on same-route navigations (#​5642)
  • fix(nextjs): Don't run webpack plugin on non-prod Vercel deployments (#​5603)
  • fix(node): Avoid catching domain errors in request handler (#​5627)
  • fix(serverless): Check for existence of callback in GCP event handler before calling (#​5608)
  • ref(nextjs): Add warning about non-hidden sourcemaps (#​5649)
  • ref(nextjs): Use proxy loader for wrapping all data-fetching functions (#​5602)
  • ref(tracing): Remove mark measurements (#​5605)
  • ref(tracing): Update long task description (#​5601)
  • chore(svelte): Detect and report SvelteKit usage (#​5594)

Work in this release contributed by @​lucas-zimerman, @​GJZwiers, and @​mohd-akram. Thank you for your contributions!


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@sentry/tracing](https://github.com/getsentry/sentry-javascript) | dependencies | minor | [`7.11.1` -> `7.12.0`](https://renovatebot.com/diffs/npm/@sentry%2ftracing/7.11.1/7.12.0) | | [@sentry/vue](https://github.com/getsentry/sentry-javascript) | dependencies | minor | [`7.11.1` -> `7.12.0`](https://renovatebot.com/diffs/npm/@sentry%2fvue/7.11.1/7.12.0) | --- ### Release Notes <details> <summary>getsentry/sentry-javascript</summary> ### [`v7.12.0`](https://github.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#&#8203;7120) [Compare Source](https://github.com/getsentry/sentry-javascript/compare/7.11.1...7.12.0) This release adds an environment check in `@sentry/nextjs` for Vercel deployments (using the `VERCEL_ENV` env variable), and only enables `SentryWebpackPlugin` if the environment is `production`. To override this, [setting `disableClientWebpackPlugin` or `disableServerWebpackPlugin` to `false`](https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/#disable-sentrywebpackplugin) now takes precedence over other checks, rather than being a no-op. Note: Overriding this is not recommended! It can increase build time and clog Release Health data in Sentry with inaccurate noise. - feat(nextjs): Create transactions in `getInitialProps` and `getServerSideProps` ([#&#8203;5593](https://github.com/getsentry/sentry-javascript/issues/5593)) - feat(nextjs): Instrument server-side `getInitialProps` of `_app`, `_document` and `_error` ([#&#8203;5604](https://github.com/getsentry/sentry-javascript/issues/5604)) - feat(node): Populate `event.contexts` for Node.js ([#&#8203;5512](https://github.com/getsentry/sentry-javascript/issues/5512)) - feat(svelte): Add Component Tracking ([#&#8203;5612](https://github.com/getsentry/sentry-javascript/issues/5612)) - fix(browser): use valid urls in Request checks ([#&#8203;5630](https://github.com/getsentry/sentry-javascript/issues/5630)) - fix(integrations): Don't add empty stack trace in `RewriteFrames` ([#&#8203;5625](https://github.com/getsentry/sentry-javascript/issues/5625)) - fix(nextjs): Start navigation transactions on same-route navigations ([#&#8203;5642](https://github.com/getsentry/sentry-javascript/issues/5642)) - fix(nextjs): Don't run webpack plugin on non-prod Vercel deployments ([#&#8203;5603](https://github.com/getsentry/sentry-javascript/issues/5603)) - fix(node): Avoid catching domain errors in request handler ([#&#8203;5627](https://github.com/getsentry/sentry-javascript/issues/5627)) - fix(serverless): Check for existence of callback in GCP event handler before calling ([#&#8203;5608](https://github.com/getsentry/sentry-javascript/issues/5608)) - ref(nextjs): Add warning about non-hidden sourcemaps ([#&#8203;5649](https://github.com/getsentry/sentry-javascript/issues/5649)) - ref(nextjs): Use proxy loader for wrapping all data-fetching functions ([#&#8203;5602](https://github.com/getsentry/sentry-javascript/issues/5602)) - ref(tracing): Remove mark measurements ([#&#8203;5605](https://github.com/getsentry/sentry-javascript/issues/5605)) - ref(tracing): Update long task description ([#&#8203;5601](https://github.com/getsentry/sentry-javascript/issues/5601)) - chore(svelte): Detect and report SvelteKit usage ([#&#8203;5594](https://github.com/getsentry/sentry-javascript/issues/5594)) Work in this release contributed by [@&#8203;lucas-zimerman](https://github.com/lucas-zimerman), [@&#8203;GJZwiers](https://github.com/GJZwiers), and [@&#8203;mohd-akram](https://github.com/mohd-akram). Thank you for your contributions! </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, click this checkbox. --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzMi4xNTMuNCIsInVwZGF0ZWRJblZlciI6IjMyLjE1My40In0=-->
renovate added the
dependencies
label 2022-09-01 20:03:34 +00:00
renovate added 1 commit 2022-09-01 20:03:34 +00:00
continuous-integration/drone/pr Build is passing Details
56322faae2
fix(deps): update sentry-javascript monorepo to v7.12.0
Member

Hi renovate!

Thank you for creating a PR!

I've deployed the changes of this PR on a preview environment under this URL: https://2307-renovate-sentry-javascript-monor--vikunja-frontend-preview.netlify.app

You can use this url to view the changes live and test them out.
You will need to manually connect this to an api running somehwere. The easiest to use is https://try.vikunja.io/.

Have a nice day!

Beep boop, I'm a bot.

Hi renovate! Thank you for creating a PR! I've deployed the changes of this PR on a preview environment under this URL: https://2307-renovate-sentry-javascript-monor--vikunja-frontend-preview.netlify.app You can use this url to view the changes live and test them out. You will need to manually connect this to an api running somehwere. The easiest to use is https://try.vikunja.io/. Have a nice day! > Beep boop, I'm a bot.
konrad merged commit 2e2eebf206 into main 2022-09-02 06:45:30 +00:00
konrad deleted branch renovate/sentry-javascript-monorepo 2022-09-02 06:45:30 +00:00
This repo is archived. You cannot comment on pull requests.
No description provided.