build(deps): bump @sentry/browser from 10.52.0 to 10.53.1#1261
build(deps): bump @sentry/browser from 10.52.0 to 10.53.1#1261dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@sentry/browser](https://github.com/getsentry/sentry-javascript) from 10.52.0 to 10.53.1. - [Release notes](https://github.com/getsentry/sentry-javascript/releases) - [Changelog](https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md) - [Commits](getsentry/sentry-javascript@10.52.0...10.53.1) --- updated-dependencies: - dependency-name: "@sentry/browser" dependency-version: 10.53.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit b2c3b85. Configure here.
| }, | ||
| "dependencies": { | ||
| "@sentry/browser": "10.52.0", | ||
| "@sentry/browser": "10.53.1", |
There was a problem hiding this comment.
Sentry sibling versions mismatched
High Severity
This change bumps @sentry/browser to 10.53.1 while @sentry/core and @sentry/types remain on 10.52.0. The SDK treats the browser version as the required sibling for all @sentry/* packages, so postinstall rejects the manifest and the lockfile can install two @sentry/core versions, which risks Sentry runtime failures.
Reviewed by Cursor Bugbot for commit b2c3b85. Configure here.
|
This pull request has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/sentry/browser-10.53.1
branch
Bumps @sentry/browser from 10.52.0 to 10.53.1.
Release notes
Sourced from @sentry/browser's releases.
... (truncated)
Changelog
Sourced from @sentry/browser's changelog.
... (truncated)
Commits
cd97408release: 10.53.166cfb25Merge pull request #20838 from getsentry/prepare-release/10.53.1df8fd38meta(changelog): Update changelog for 10.53.15881009fix(core): Include subpath type shims in published package (#20835)6a7d179fix(core): Don't gate user data for streamed spans at scope read time (#20827)ad47c3cref(hono): Consolidate route patching and add clarification comments (#20829)28d6fe5Merge pull request #20826 from getsentry/master46aca45Merge branch 'release/10.53.0'b5cbc9cchore(deps): Bump next from 15.5.15 to 15.5.18 in /dev-packages/e2e-tests/tes...05489b8release: 10.53.0Dependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)