Bump the sentry group with 3 updates #2898

dependabot · 2025-03-28T02:04:21Z

Bumps the sentry group with 3 updates: @sentry/browser, @sentry/react and @sentry/types.

Updates @sentry/browser from 9.9.0 to 9.10.0

Release notes

Sourced from @sentry/browser's releases.

9.10.0

Important Changes
feat: Add support for logs

feat(node): Add logging public APIs to Node SDKs (#15764)

feat(core): Add support for beforeSendLog (#15814)

feat(core): Add support for parameterizing logs (#15812)

fix: Remove critical log severity level (#15824)

All JavaScript SDKs other than @sentry/cloudflare and @sentry/deno now support sending logs via dedicated methods as part of Sentry's upcoming logging product.

Logging is gated by an experimental option, _experiments.enableLogs.
Sentry.init({
  dsn: 'PUBLIC_DSN',
  // `enableLogs` must be set to true to use the logging features
  _experiments: { enableLogs: true },
});
const { trace, debug, info, warn, error, fatal, fmt } = Sentry.logger;
trace('Starting database connection', { database: 'users' });
debug('Cache miss for user', { userId: 123 });
error('Failed to process payment', { orderId: 'order_123', amount: 99.99 });
fatal('Database connection pool exhausted', { database: 'users', activeConnections: 100 });
// Structured logging via the fmt helper function. When you use fmt, the string template and parameters are sent separately so they can be queried independently in Sentry.
info(fmt(Updated profile for user ${userId}));
warn(fmt(Rate limit approaching for endpoint ${endpoint}. Requests: ${requests}, Limit: ${limit}));
With server-side SDKs like @sentry/node, @sentry/bun or server-side of @sentry/nextjs or @sentry/sveltekit, you can do structured logging without needing the fmt helper function.
const { info, warn } = Sentry.logger;
info('User %s logged in successfully', [123]);
warn('Failed to load user %s data', [123], { errorCode: 404 });
To filter logs, or update them before they are sent to Sentry, you can use the _experiments.beforeSendLog option.
feat(browser): Add diagnoseSdkConnectivity() function to programmatically detect possible connectivity issues (#15821)

The diagnoseSdkConnectivity() function can be used to programmatically detect possible connectivity issues with the Sentry SDK.

... (truncated)

Changelog

Sourced from @sentry/browser's changelog.

9.10.0

Important Changes
feat: Add support for logs

feat(node): Add logging public APIs to Node SDKs (#15764)

feat(core): Add support for beforeSendLog (#15814)

feat(core): Add support for parameterizing logs (#15812)

fix: Remove critical log severity level (#15824)

All JavaScript SDKs other than @sentry/cloudflare and @sentry/deno now support sending logs via dedicated methods as part of Sentry's upcoming logging product.

Logging is gated by an experimental option, _experiments.enableLogs.
Sentry.init({
  dsn: 'PUBLIC_DSN',
  // `enableLogs` must be set to true to use the logging features
  _experiments: { enableLogs: true },
});
const { trace, debug, info, warn, error, fatal, fmt } = Sentry.logger;
trace('Starting database connection', { database: 'users' });
debug('Cache miss for user', { userId: 123 });
error('Failed to process payment', { orderId: 'order_123', amount: 99.99 });
fatal('Database connection pool exhausted', { database: 'users', activeConnections: 100 });
// Structured logging via the fmt helper function. When you use fmt, the string template and parameters are sent separately so they can be queried independently in Sentry.
info(fmt(Updated profile for user ${userId}));
warn(fmt(Rate limit approaching for endpoint ${endpoint}. Requests: ${requests}, Limit: ${limit}));
With server-side SDKs like @sentry/node, @sentry/bun or server-side of @sentry/nextjs or @sentry/sveltekit, you can do structured logging without needing the fmt helper function.
const { info, warn } = Sentry.logger;
info('User %s logged in successfully', [123]);
warn('Failed to load user %s data', [123], { errorCode: 404 });
To filter logs, or update them before they are sent to Sentry, you can use the _experiments.beforeSendLog option.
feat(browser): Add diagnoseSdkConnectivity() function to programmatically detect possible connectivity issues (#15821)

The diagnoseSdkConnectivity() function can be used to programmatically detect possible connectivity issues with the Sentry SDK.

... (truncated)

Commits

e383fff release: 9.10.0
03d4ab1 Merge pull request #15867 from getsentry/prepare-release/9.10.0
d430d96 meta(changelog): Update changelog for 9.10.0
ef2f35d ref(opentelemetry): Avoid sampling work for non-root spans (#15820)
2284e81 deps: Bump bundler plugins to 3.2.3 (#15829)
b0a1b06 test: Add browser and nodejs integration tests for logs (#15815)
7191ebd feat: Always truncate stored breadcrumb messages to 2kb (#15819)
05391d0 feat(node): Only add span listeners for instrumentation when used (#15802)
c38315e chore(jest): Final Jest cleanup (#15549)
12c5e73 test(google-serverless): Migrate to Vitest (#15567)
Additional commits viewable in compare view

Updates @sentry/react from 9.9.0 to 9.10.0

Release notes

Sourced from @sentry/react's releases.

9.10.0

Important Changes
feat: Add support for logs

feat(node): Add logging public APIs to Node SDKs (#15764)

feat(core): Add support for beforeSendLog (#15814)

feat(core): Add support for parameterizing logs (#15812)

fix: Remove critical log severity level (#15824)

All JavaScript SDKs other than @sentry/cloudflare and @sentry/deno now support sending logs via dedicated methods as part of Sentry's upcoming logging product.

Logging is gated by an experimental option, _experiments.enableLogs.
Sentry.init({
  dsn: 'PUBLIC_DSN',
  // `enableLogs` must be set to true to use the logging features
  _experiments: { enableLogs: true },
});
const { trace, debug, info, warn, error, fatal, fmt } = Sentry.logger;
trace('Starting database connection', { database: 'users' });
debug('Cache miss for user', { userId: 123 });
error('Failed to process payment', { orderId: 'order_123', amount: 99.99 });
fatal('Database connection pool exhausted', { database: 'users', activeConnections: 100 });
// Structured logging via the fmt helper function. When you use fmt, the string template and parameters are sent separately so they can be queried independently in Sentry.
info(fmt(Updated profile for user ${userId}));
warn(fmt(Rate limit approaching for endpoint ${endpoint}. Requests: ${requests}, Limit: ${limit}));
With server-side SDKs like @sentry/node, @sentry/bun or server-side of @sentry/nextjs or @sentry/sveltekit, you can do structured logging without needing the fmt helper function.
const { info, warn } = Sentry.logger;
info('User %s logged in successfully', [123]);
warn('Failed to load user %s data', [123], { errorCode: 404 });
To filter logs, or update them before they are sent to Sentry, you can use the _experiments.beforeSendLog option.
feat(browser): Add diagnoseSdkConnectivity() function to programmatically detect possible connectivity issues (#15821)

The diagnoseSdkConnectivity() function can be used to programmatically detect possible connectivity issues with the Sentry SDK.

... (truncated)

Changelog

Sourced from @sentry/react's changelog.

9.10.0

Important Changes
feat: Add support for logs

feat(node): Add logging public APIs to Node SDKs (#15764)

feat(core): Add support for beforeSendLog (#15814)

feat(core): Add support for parameterizing logs (#15812)

fix: Remove critical log severity level (#15824)

All JavaScript SDKs other than @sentry/cloudflare and @sentry/deno now support sending logs via dedicated methods as part of Sentry's upcoming logging product.

Logging is gated by an experimental option, _experiments.enableLogs.
Sentry.init({
  dsn: 'PUBLIC_DSN',
  // `enableLogs` must be set to true to use the logging features
  _experiments: { enableLogs: true },
});
const { trace, debug, info, warn, error, fatal, fmt } = Sentry.logger;
trace('Starting database connection', { database: 'users' });
debug('Cache miss for user', { userId: 123 });
error('Failed to process payment', { orderId: 'order_123', amount: 99.99 });
fatal('Database connection pool exhausted', { database: 'users', activeConnections: 100 });
// Structured logging via the fmt helper function. When you use fmt, the string template and parameters are sent separately so they can be queried independently in Sentry.
info(fmt(Updated profile for user ${userId}));
warn(fmt(Rate limit approaching for endpoint ${endpoint}. Requests: ${requests}, Limit: ${limit}));
With server-side SDKs like @sentry/node, @sentry/bun or server-side of @sentry/nextjs or @sentry/sveltekit, you can do structured logging without needing the fmt helper function.
const { info, warn } = Sentry.logger;
info('User %s logged in successfully', [123]);
warn('Failed to load user %s data', [123], { errorCode: 404 });
To filter logs, or update them before they are sent to Sentry, you can use the _experiments.beforeSendLog option.
feat(browser): Add diagnoseSdkConnectivity() function to programmatically detect possible connectivity issues (#15821)

The diagnoseSdkConnectivity() function can be used to programmatically detect possible connectivity issues with the Sentry SDK.

... (truncated)

Commits

e383fff release: 9.10.0
03d4ab1 Merge pull request #15867 from getsentry/prepare-release/9.10.0
d430d96 meta(changelog): Update changelog for 9.10.0
ef2f35d ref(opentelemetry): Avoid sampling work for non-root spans (#15820)
2284e81 deps: Bump bundler plugins to 3.2.3 (#15829)
b0a1b06 test: Add browser and nodejs integration tests for logs (#15815)
7191ebd feat: Always truncate stored breadcrumb messages to 2kb (#15819)
05391d0 feat(node): Only add span listeners for instrumentation when used (#15802)
c38315e chore(jest): Final Jest cleanup (#15549)
12c5e73 test(google-serverless): Migrate to Vitest (#15567)
Additional commits viewable in compare view

Updates @sentry/types from 9.9.0 to 9.10.0

Release notes

Sourced from @sentry/types's releases.

9.10.0

Important Changes
feat: Add support for logs

feat(node): Add logging public APIs to Node SDKs (#15764)

feat(core): Add support for beforeSendLog (#15814)

feat(core): Add support for parameterizing logs (#15812)

fix: Remove critical log severity level (#15824)

All JavaScript SDKs other than @sentry/cloudflare and @sentry/deno now support sending logs via dedicated methods as part of Sentry's upcoming logging product.

Logging is gated by an experimental option, _experiments.enableLogs.
Sentry.init({
  dsn: 'PUBLIC_DSN',
  // `enableLogs` must be set to true to use the logging features
  _experiments: { enableLogs: true },
});
const { trace, debug, info, warn, error, fatal, fmt } = Sentry.logger;
trace('Starting database connection', { database: 'users' });
debug('Cache miss for user', { userId: 123 });
error('Failed to process payment', { orderId: 'order_123', amount: 99.99 });
fatal('Database connection pool exhausted', { database: 'users', activeConnections: 100 });
// Structured logging via the fmt helper function. When you use fmt, the string template and parameters are sent separately so they can be queried independently in Sentry.
info(fmt(Updated profile for user ${userId}));
warn(fmt(Rate limit approaching for endpoint ${endpoint}. Requests: ${requests}, Limit: ${limit}));
With server-side SDKs like @sentry/node, @sentry/bun or server-side of @sentry/nextjs or @sentry/sveltekit, you can do structured logging without needing the fmt helper function.
const { info, warn } = Sentry.logger;
info('User %s logged in successfully', [123]);
warn('Failed to load user %s data', [123], { errorCode: 404 });
To filter logs, or update them before they are sent to Sentry, you can use the _experiments.beforeSendLog option.
feat(browser): Add diagnoseSdkConnectivity() function to programmatically detect possible connectivity issues (#15821)

The diagnoseSdkConnectivity() function can be used to programmatically detect possible connectivity issues with the Sentry SDK.

... (truncated)

Changelog

Sourced from @sentry/types's changelog.

9.10.0

Important Changes
feat: Add support for logs

feat(node): Add logging public APIs to Node SDKs (#15764)

feat(core): Add support for beforeSendLog (#15814)

feat(core): Add support for parameterizing logs (#15812)

fix: Remove critical log severity level (#15824)

All JavaScript SDKs other than @sentry/cloudflare and @sentry/deno now support sending logs via dedicated methods as part of Sentry's upcoming logging product.

Logging is gated by an experimental option, _experiments.enableLogs.
Sentry.init({
  dsn: 'PUBLIC_DSN',
  // `enableLogs` must be set to true to use the logging features
  _experiments: { enableLogs: true },
});
const { trace, debug, info, warn, error, fatal, fmt } = Sentry.logger;
trace('Starting database connection', { database: 'users' });
debug('Cache miss for user', { userId: 123 });
error('Failed to process payment', { orderId: 'order_123', amount: 99.99 });
fatal('Database connection pool exhausted', { database: 'users', activeConnections: 100 });
// Structured logging via the fmt helper function. When you use fmt, the string template and parameters are sent separately so they can be queried independently in Sentry.
info(fmt(Updated profile for user ${userId}));
warn(fmt(Rate limit approaching for endpoint ${endpoint}. Requests: ${requests}, Limit: ${limit}));
With server-side SDKs like @sentry/node, @sentry/bun or server-side of @sentry/nextjs or @sentry/sveltekit, you can do structured logging without needing the fmt helper function.
const { info, warn } = Sentry.logger;
info('User %s logged in successfully', [123]);
warn('Failed to load user %s data', [123], { errorCode: 404 });
To filter logs, or update them before they are sent to Sentry, you can use the _experiments.beforeSendLog option.
feat(browser): Add diagnoseSdkConnectivity() function to programmatically detect possible connectivity issues (#15821)

The diagnoseSdkConnectivity() function can be used to programmatically detect possible connectivity issues with the Sentry SDK.

... (truncated)

Commits

e383fff release: 9.10.0
03d4ab1 Merge pull request #15867 from getsentry/prepare-release/9.10.0
d430d96 meta(changelog): Update changelog for 9.10.0
ef2f35d ref(opentelemetry): Avoid sampling work for non-root spans (#15820)
2284e81 deps: Bump bundler plugins to 3.2.3 (#15829)
b0a1b06 test: Add browser and nodejs integration tests for logs (#15815)
7191ebd feat: Always truncate stored breadcrumb messages to 2kb (#15819)
05391d0 feat(node): Only add span listeners for instrumentation when used (#15802)
c38315e chore(jest): Final Jest cleanup (#15549)
12c5e73 test(google-serverless): Migrate to Vitest (#15567)
Additional commits viewable in compare view

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the sentry group with 3 updates: [@sentry/browser](https://github.com/getsentry/sentry-javascript), [@sentry/react](https://github.com/getsentry/sentry-javascript) and [@sentry/types](https://github.com/getsentry/sentry-javascript). Updates `@sentry/browser` from 9.9.0 to 9.10.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@9.9.0...9.10.0) Updates `@sentry/react` from 9.9.0 to 9.10.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@9.9.0...9.10.0) Updates `@sentry/types` from 9.9.0 to 9.10.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@9.9.0...9.10.0) --- updated-dependencies: - dependency-name: "@sentry/browser" dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sentry - dependency-name: "@sentry/react" dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sentry - dependency-name: "@sentry/types" dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sentry ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot · 2025-03-28T08:16:58Z

Looks like these dependencies are no longer updatable, so this is no longer needed.

dependabot bot added dependencies javascript labels Mar 28, 2025

dependabot bot requested a review from a team as a code owner March 28, 2025 02:04

dependabot bot closed this Mar 28, 2025

dependabot bot deleted the dependabot/npm_and_yarn/sentry-7b34ca9d67 branch March 28, 2025 08:17

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bump the sentry group with 3 updates #2898

Bump the sentry group with 3 updates #2898

dependabot bot commented on behalf of github Mar 28, 2025 •

edited

Loading

dependabot bot commented on behalf of github Mar 28, 2025

Bump the sentry group with 3 updates #2898

Bump the sentry group with 3 updates #2898

Conversation

dependabot bot commented on behalf of github Mar 28, 2025 • edited Loading

9.10.0

Important Changes

9.10.0

Important Changes

9.10.0

Important Changes

9.10.0

Important Changes

9.10.0

Important Changes

9.10.0

Important Changes

dependabot bot commented on behalf of github Mar 28, 2025

dependabot bot commented on behalf of github Mar 28, 2025 •

edited

Loading