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.
fix(browser): use valid urls in Request checks (#5630)
fix(integrations): Don't add empty stack trace in RewriteFrames (#5625)
feat(nextjs): Create transactions in getInitialProps and getServerSideProps (#5593)
feat(nextjs): Instrument server-side getInitialProps of _app, _document and _error (#5604)
fix(nextjs): Start navigation transactions on same-route navigations (#5642)
fix(nextjs): Don't run webpack plugin on non-prod Vercel deployments (#5603)
ref(nextjs): Add warning about non-hidden sourcemaps (#5649)
ref(nextjs): Use proxy loader for wrapping all data-fetching functions (#5602)
feat(node): Populate event.contexts for Node.js (#5512)
fix(node): Avoid catching domain errors in request handler (#5627)
fix(serverless): Check for existence of callback in GCP event handler before calling (#5608)
fix(remix): Store transaction on express req (#5595)
7.11.0
This release introduces updates the tracingOrigins option to not attach any headers/create an spans when supplied with an empty array ([]). Previously, we would supply the default tracingOrigins if an empty array was set as the tracingOrigins option.
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)
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 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)
dependabot[bot]
commented
1 year ago
Bumps @sentry/browser from 6.11.0 to 7.13.0.
Release notes
Sourced from
@sentry/browser's releases.... (truncated)
Changelog
Sourced from
@sentry/browser's changelog.... (truncated)
Commits
3ea3848release: 7.13.03c77f62meta: CHANGELOG for 7.13.0 (#5748)51bc032ref(tracing): Use previous source when logging name changes (#5733)347fbe4ref: Make dynamic sampling context mutable (#5710)e26e43achore(deps): Add@types/rimraf(#5743)180f644fix(nextjs): MakeNextApiHandlertype version-agnostic (#5737)fbd4ef0ref(core): Use timestamp of processed event in name change (#5735)ff4f97ffeat(core): Set custom transaction source for event processors (#5722)8cff038ref(node): Add propagations to http integration (#5720)60b394aref(tracing): Add propagations to tracing SDK (#5719)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 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)