Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/preview-pr.yml
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ concurrency:
cancel-in-progress: true

env:
NODE_VERSION: '24.12.0'
NODE_VERSION: '24.22.3'

jobs:
# ✅ Runs for all PRs (including forks)
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/vercel-prod-on-release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ on:
types: [published]

env:
NODE_VERSION: '24.12.0'
NODE_VERSION: '24.22.3'

jobs:
deploy:
Expand Down
1 change: 1 addition & 0 deletions .nvmrc
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
24.22.3
3 changes: 3 additions & 0 deletions src/instrumentation.ts
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,9 @@

export async function register(): Promise<void> {
if (process.env.NEXT_RUNTIME === 'nodejs') {
// Log the runtime Node version once per instance start. Vercel picks the
// patch version itself, so this is how we confirm it in production logs.
console.info(`Node.js runtime ${process.version}`);

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[suggestion]: The instrumentation.ts log isn't needed for the upgrade. Sentry already reports the Node version in the Runtime context of every server event, and this would log on every cold start. Could we drop it and check Sentry after the release instead?

// Initialize Sentry for the Node.js runtime
await import('../sentry.server.config');
}
Expand Down
Loading