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.
fix(core): Suppress stack when SentryError isn't an error (#5562)
feat(tracing): Allow for setting of an empty array (#5583)
7.10.0
This release introduces the first alpha version of @sentry/svelte, our newest JavaScript SDK! For details on how to use it, please see the README and the tracking GitHub issue.
feat(react): Track duration of React component updates (#5531)
feat(svelte): Add Error and Performance Instrumentation from Browser SDK (#5543)
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)
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.
fix(core): Suppress stack when SentryError isn't an error (#5562)
feat(tracing): Allow for setting of an empty array (#5583)
7.10.0
This release introduces the first alpha version of @sentry/svelte, our newest JavaScript SDK! For details on how to use it, please see the README and the tracking GitHub issue.
feat(react): Track duration of React component updates (#5531)
feat(svelte): Add Error and Performance Instrumentation from Browser SDK (#5543)
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)
Bumps @sentry/integrations from 7.3.0 to 7.12.0.
Release notes
Sourced from
@sentry/integrations
's releases.... (truncated)
Changelog
Sourced from
@sentry/integrations
's changelog.... (truncated)
Commits
e3fbee5
release: 7.12.0b5a7c03
fix: Adjust changelog 7.12.0 heading level (#5663)b92d422
fix: changelog for 7.12.0 (#5662)b26c611
meta: Update changelog with 7.12.0 (#5661)f683059
feat(svelte): Add Component Tracking (#5612)27b5771
ref(nextjs): Add warning about non-hidden sourcemaps (#5649)7542482
chore(various): Fix comments and docstrings (#5651)aff06e0
chore(utils): UpdateparseBaggageSetMutability
docstring (#5657)51c016f
fix(integrations): Don't add empty stack trace inRewriteFrames
(#5625)232964c
ref(tests): AddTestEnv
class to Node integration tests. (#5633)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)