-
Notifications
You must be signed in to change notification settings - Fork 3
Commit 41cfac1
authored
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4&size=40){kind=avatar}
build(deps): bump @sentry/react from 9.5.0 to 9.9.0 (#681)
Bumps [@sentry/react](https://github.com/getsentry/sentry-javascript)
from 9.5.0 to 9.9.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/getsentry/sentry-javascript/releases"><code>@sentry/react</code>'s
releases</a>.</em></p>
<blockquote>
<h2>9.9.0</h2>
<h3>Important Changes</h3>
<ul>
<li>
<p><strong>feat(nextjs): Support <code>instrumentation-client.ts</code>
(<a
href="https://redirect.github.com/getsentry/sentry-javascript/pull/15705">#15705</a>)</strong></p>
<p>Next.js recently added a feature to support <a
href="https://nextjs.org/docs/app/api-reference/config/next-config-js/clientInstrumentationHook">client-side
(browser) instrumentation via the
<code>experimental.clientInstrumentationHook</code> flag and the
<code>instrumentation-client.ts</code> file</a>.</p>
<p>To be forwards compatible, the Sentry Next.js SDK will now pick up
<code>instrumentation-client.ts</code> files even on older Next.js
versions and add them to your client bundles.
It is suggested that you either rename your
<code>sentry.client.config.ts</code> file to
<code>instrumentation-client.ts</code>, or if you already happen to have
a <code>instrumentation-client.ts</code> file move the contents of
<code>sentry.client.config.ts</code> to
<code>instrumentation-client.ts</code>.</p>
</li>
<li>
<p><strong>feat(browser): Add <code>previous_trace</code> span links (<a
href="https://redirect.github.com/getsentry/sentry-javascript/pull/15569">#15569</a>)</strong></p>
<p>The <code>@sentry/browser</code> SDK and SDKs based on
<code>@sentry/browser</code> now emits a link from the first root span
of a newly started trace to the root span of a previously started trace.
You can control this feature via an option in
<code>browserTracingIntegration()</code>:</p>
<pre lang="js"><code>Sentry.init({
dsn: 'your-dsn-here'
integrations: [
Sentry.browserTracingIntegration({
// Available settings:
// - 'in-memory' (default): Stores previous trace information in memory
// - 'session-storage': Stores previous trace information in the
browser's `sessionStorage`
// - 'off': Disable storing and sending previous trace information
linkPreviousTrace: 'in-memory',
}),
],
});
</code></pre>
</li>
<li>
<p><strong>feat(browser): Add <code>logger.X</code> methods to browser
SDK (<a
href="https://redirect.github.com/getsentry/sentry-javascript/pull/15763">#15763</a>)</strong></p>
<p>For Sentry's <a
href="https://github.com/getsentry/sentry/discussions/86804">upcoming
logging product</a>, the SDK now supports sending logs via dedicated</p>
<pre lang="js"><code>Sentry.init({
dsn: 'your-dsn-here',
_experiments: {
enableLogs: true, // This is required to use the logging features
},
});
<p>Sentry.logger.info('This is a trace message', { userId: 123 });<br />
// See PR for better documentation<br />
</code></pre></p>
<p>Please note that the logs product is still in early access. See the
link above for more information.</p>
</li>
</ul>
<h3>Other Changes</h3>
<ul>
<li>feat(browser): Attach host as part of error message to "Failed
to fetch" errors (<a
href="https://redirect.github.com/getsentry/sentry-javascript/pull/15729">#15729</a>)</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md"><code>@sentry/react</code>'s
changelog</a>.</em></p>
<blockquote>
<h2>9.9.0</h2>
<h3>Important Changes</h3>
<ul>
<li>
<p><strong>feat(nextjs): Support <code>instrumentation-client.ts</code>
(<a
href="https://redirect.github.com/getsentry/sentry-javascript/pull/15705">#15705</a>)</strong></p>
<p>Next.js recently added a feature to support <a
href="https://nextjs.org/docs/app/api-reference/config/next-config-js/clientInstrumentationHook">client-side
(browser) instrumentation via the
<code>experimental.clientInstrumentationHook</code> flag and the
<code>instrumentation-client.ts</code> file</a>.</p>
<p>To be forwards compatible, the Sentry Next.js SDK will now pick up
<code>instrumentation-client.ts</code> files even on older Next.js
versions and add them to your client bundles.
It is suggested that you either rename your
<code>sentry.client.config.ts</code> file to
<code>instrumentation-client.ts</code>, or if you already happen to have
a <code>instrumentation-client.ts</code> file move the contents of
<code>sentry.client.config.ts</code> to
<code>instrumentation-client.ts</code>.</p>
</li>
<li>
<p><strong>feat(browser): Add <code>previous_trace</code> span links (<a
href="https://redirect.github.com/getsentry/sentry-javascript/pull/15569">#15569</a>)</strong></p>
<p>The <code>@sentry/browser</code> SDK and SDKs based on
<code>@sentry/browser</code> now emits a link from the first root span
of a newly started trace to the root span of a previously started trace.
You can control this feature via an option in
<code>browserTracingIntegration()</code>:</p>
<pre lang="js"><code>Sentry.init({
dsn: 'your-dsn-here'
integrations: [
Sentry.browserTracingIntegration({
// Available settings:
// - 'in-memory' (default): Stores previous trace information in memory
// - 'session-storage': Stores previous trace information in the
browser's `sessionStorage`
// - 'off': Disable storing and sending previous trace information
linkPreviousTrace: 'in-memory',
}),
],
});
</code></pre>
</li>
<li>
<p><strong>feat(browser): Add <code>logger.X</code> methods to browser
SDK (<a
href="https://redirect.github.com/getsentry/sentry-javascript/pull/15763">#15763</a>)</strong></p>
<p>For Sentry's <a
href="https://github.com/getsentry/sentry/discussions/86804">upcoming
logging product</a>, the SDK now supports sending logs via dedicated</p>
<pre lang="js"><code>Sentry.init({
dsn: 'your-dsn-here',
_experiments: {
enableLogs: true, // This is required to use the logging features
},
});
<p>Sentry.logger.info('This is a trace message', { userId: 123 });<br />
// See PR for better documentation<br />
</code></pre></p>
<p>Please note that the logs product is still in early access. See the
link above for more information.</p>
</li>
</ul>
<h3>Other Changes</h3>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/getsentry/sentry-javascript/commit/43c4c8347978a5cc08fe461d99430e380d09ef08"><code>43c4c83</code></a>
release: 9.9.0</li>
<li><a
href="https://github.com/getsentry/sentry-javascript/commit/80e19f2aa7cd3980aebdbb7290750b4a579e57c7"><code>80e19f2</code></a>
Merge pull request <a
href="https://redirect.github.com/getsentry/sentry-javascript/issues/15791">#15791</a>
from getsentry/prepare-release/9.9.0</li>
<li><a
href="https://github.com/getsentry/sentry-javascript/commit/bb358cf86ce303b4f320060ccee1b1d7c73676ba"><code>bb358cf</code></a>
meta: Update changelog for 9.9.0</li>
<li><a
href="https://github.com/getsentry/sentry-javascript/commit/0cf8ec2637cff9cff12c34e2996fd146172f6d82"><code>0cf8ec2</code></a>
feat(browser): Attach host as part of error message to "Failed to
fetch" erro...</li>
<li><a
href="https://github.com/getsentry/sentry-javascript/commit/79ff8f27513829be53f4ebd168dc7e207bfd2828"><code>79ff8f2</code></a>
fix(nuxt): Delete no longer needed Nitro 'close' hook (<a
href="https://redirect.github.com/getsentry/sentry-javascript/issues/15790">#15790</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-javascript/commit/006479c7f9818236868187e298b761fc02b17a4c"><code>006479c</code></a>
ref(nextjs): Fix Next.js vercel-edge runtime package information (<a
href="https://redirect.github.com/getsentry/sentry-javascript/issues/15789">#15789</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-javascript/commit/57f04e0385ef403d188d9fb79c78398cfc50942e"><code>57f04e0</code></a>
ref: Remove some usages of <code>dropUndefinedKeys()</code> (<a
href="https://redirect.github.com/getsentry/sentry-javascript/issues/15781">#15781</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-javascript/commit/50d2514a032fc2dd3d51dc9266bd40b9a4621d0e"><code>50d2514</code></a>
feat(node): Add fastify <code>shouldHandleError</code> (<a
href="https://redirect.github.com/getsentry/sentry-javascript/issues/15771">#15771</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-javascript/commit/ba5993caaa2bef98e85e1c2d82ce47e2817bff8c"><code>ba5993c</code></a>
feat(core): Add <code>parseStringToURL</code> method (<a
href="https://redirect.github.com/getsentry/sentry-javascript/issues/15768">#15768</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-javascript/commit/e55b8ee049923c4e17ed79df492495cfc2f47726"><code>e55b8ee</code></a>
feat(browser): Add logger.X methods to browser SDK (<a
href="https://redirect.github.com/getsentry/sentry-javascript/issues/15763">#15763</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/getsentry/sentry-javascript/compare/9.5.0...9.9.0">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
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-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
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)
</details>
Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>1 parent 7a45fe8 commit 41cfac1Copy full SHA for 41cfac1
2 files changed
+70
-70
lines changed+69-69
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
+1-1
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
6 | 6 | | |
7 | 7 | | |
8 | 8 | | |
9 | | - | |
| 9 | + | |
10 | 10 | | |
11 | 11 | | |
12 | 12 | | |
| |||
0 commit comments