You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore(deps): bump @sentry/nextjs from 10.33.0 to 10.75.2 - #21583
fix(v10/cloudflare): Enforce flush timeout across Workflow lifecycle (#24582)
fix(v10/core): Apply dataCollection.urlQueryParams to collected URLs and query strings (#24572)
fix(v10/nextjs): Align tunnel request matching in middleware with tunnel rewrite (#24565)
fix(v10/node): Stop leaking unhandled rejections on aborted Vercel AI streams (#24563)
10.75.1
fix(v10/cloudflare): Capture telemetry from untraced Durable Object RPC calls (#24512)
fix(v10/cloudflare): Instrument namespaces returned by jurisdiction() (#24513)
fix(v10/hono): Allow @cloudflare/workers-types v5 as peer dependency (#24500)
fix(v10/nextjs): Resolve Next.js version relative to the SDK when cwd differs (#24475)
10.75.0
Important Changes
feat(v10/effect): Capture errors through the Effect v4 ErrorReporter API (#24445)
On Effect v4, Sentry.effectLayer now registers a Sentry ErrorReporter. Failures that pass through Effect.withErrorReporting, ErrorReporter.report or the built-in HTTP and RPC reporting boundaries are captured automatically, with ErrorReporter.ignore, ErrorReporter.severity and ErrorReporter.attributes annotations respected. Nothing changes on Effect v3.
Other Changes
feat(v10/core): Accept a CollectBehavior shorthand for dataCollection.httpHeaders (#24339)
fix(v10/browser): Release the XHR virtualError once the request completed (#24307)
fix(v10/browser-utils): Skip nullish LCP entries in vendored web-vitals (#24349)
fix(v10/bundler-plugins): Stamp debug IDs onto emitted source maps when disable-upload is set (#24332)
fix(v10/core): Don't instrument the SDK's own envelope requests (#24276)
fix(v10/nextjs): Only include emitted chunk directories in Turbopack sourcemap upload (#24295)
fix(v10/nitro): Import from nitro/h3 instead of h3 directly (#24444)
fix(v10/node-core): Don't recurse in logAndExitProcess on a broken stdio pipe (#24353)
fix(v10/nuxt): Detect Nitro version via the app's Nuxt dependency chain (#24025)
fix(v10/replay): Don't rewrite already-emitted nodes when syncing mirror attributes (#23588)
Most Recent Ignore Conditions Applied to This Pull Request
Dependency Name
Ignore Conditions
@sentry/nextjs
[>= 10.32.a, < 10.33]
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 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)
You can disable automated security fix PRs for this repo from the Security Alerts page.
Summary by CodeRabbit
Chores
This update does not include changes to app features, behavior, or the user experience. There are no new capabilities, bug fixes, or interface changes to highlight in these release notes.
Note: This PR has failing CircleCI checks.
BLEnder cannot access CircleCI log output, so it
may not be able to diagnose or fix the failure.
Consider migrating CI to GitHub Actions so BLEnder
can read failure logs directly.
BLEnder could not fix this PR automatically. Workflow run
I couldn't fix this one, and I've made no changes.
I couldn't reproduce the failure. The installed node_modules still has @ sentry/nextjs 10.33.0, and yarn install can't fetch the new packages. Every attempt failed with ERR_SOCKET_CLOSED_BEFORE_CONNECTION when connecting to registry.yarnpkg.com, even with that host explicitly allowed. So I don't know the root cause for certain.
Likely cause (not confirmed): the bump only raised @ sentry/nextjs. @ sentry/browser, @ sentry/nestjs, @ sentry/node and @ sentry/opentelemetry are still pinned at ^10.33.0. The lockfile now holds two copies of @ sentry/core, at 10.75.2 and 10.76.2. That kind of version mix commonly breaks the build.
Suggested fix: in the root package.json, set those four packages to ^10.75.2. Then run yarn install with registry access and commit the updated yarn.lock. I tried exactly this, but undid it because I couldn't regenerate the lockfile. Changing package.json alone would break CI's --immutable install.
I didn't write .blender-commit-msg, since there's nothing to commit.
Auto reviews are limited based on label configuration.
🏷️ Required labels (at least one): 1
coderabbit
Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.
No actionable merge-blocking risk is identified in this dependency-range update.
Architecture risk: Low · up to 015c5
The change affects 1 system.
Changed systems:package.json
Architecture concerns
No architecture-level concerns identified.
Review details
Systems and components
observed — package.json (service) was modified; 1 changed file maps to changed impact.
Before / after behavior
observed — Modified behavior in package.json: The five Sentry dependencies listed are updated from version range ^10.33.0 to ^10.78.0.
Pre-merge checks: 5
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title accurately identifies the Sentry dependency upgrade, but it names only @sentry/nextjs and version 10.75.2. The changeset updates five Sentry packages to ^10.78.0.
Docstring Coverage
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Finishing Touches
Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
CodeRabbit Verify
Run CodeRabbit Verify to test the changes in this pull request.
Recent review info
Run configuration
Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: defaults
Review profile: CHILL
Plan: Enterprise
Run ID: 9fe214e8-d396-4122-a0e6-61ba3f0a9d92
Commits
Reviewing files that changed from the base of the PR and between d4d9155 and 015c52e.
Files ignored due to path filters: 1
yarn.lock is excluded by !**/yarn.lock, !**/*.lock
Files selected for processing: 1
package.json
Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review.
Because:
- bumping only @sentry/nextjs left browser, nestjs, node and opentelemetry on 10.33, so two @sentry/core type sets broke the build with TS2322
This commit:
- moves @sentry/browser, nestjs, nextjs, node and opentelemetry to ^10.78.0
- dedupes @sentry/* in yarn.lock to a single @sentry/core
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
dependabot
Bot
added
dependencies
![mozilla-blender[bot]](https://avatars.githubusercontent.com/in/3479298?s=60&v=4){kind=small}
Bumps @sentry/nextjs from 10.33.0 to 10.75.2.
Changelog
Sourced from @sentry/nextjs's changelog.
... (truncated)
Commits
faeac9arelease: 10.75.27175b19meta(changelog): Update changelog for 10.75.2 (#24585)8f5dc60fix(v10/cloudflare): Enforce flush timeout across Workflow lifecycle (#24582)44506dffix(v10/node): Stop leaking unhandled rejections on aborted Vercel AI streams...c0eb753fix(v10/core): ApplydataCollection.urlQueryParamsto collected URLs and qu...d525a2ffix(v10/nextjs): Align tunnel request matching in middleware with tunnel rewr...5b03e28Merge remote-tracking branch 'remotes/origin/release/10.75.1' into v108025a92release: 10.75.1d1462b2meta(changelog): Update changelog for 10.75.1 (#24561)c8f750ffix(v10/cloudflare): Capture telemetry from untraced Durable Object RPC calls...Most Recent Ignore Conditions Applied to This Pull Request
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 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)You can disable automated security fix PRs for this repo from the Security Alerts page.
Summary by CodeRabbit