Skip to content

[v9] Don't rely on Next.js Build ID for release names #14940

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
lforst opened this issue Jan 8, 2025 · 0 comments · Fixed by #14939
Closed

[v9] Don't rely on Next.js Build ID for release names #14940

lforst opened this issue Jan 8, 2025 · 0 comments · Fixed by #14939
Assignees
@lforst
Milestone
9.0.0

Comments

@lforst
Copy link
Contributor

lforst commented Jan 8, 2025

Description

The future of the availability of the Next.js Build ID is uncertain with Turbopack. In preparation, we should not rely on it for release names and instead attempt to use git commit shas. As an added benefit, the Build ID was non-deterministic and caused issues for users who relied on deterministic builds (it also caused cache busts).

The history of thoughts around this change is outlined in this comment: #14303 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lforst lforst

Labels
None yet
Projects
None yet
Milestone
9.0.0
Development

Successfully merging a pull request may close this issue.

feat(nextjs)!: Don't rely on Next.js Build ID for release names getsentry/sentry-javascript
1 participant
@lforst