Skip to content

Update One-Click Catalyst flow to specify Node v24#2937

Merged
BigEth4n merged 1 commit intocanaryfrom
Update-Node-Version-for-OCC-Flow
Mar 19, 2026
Merged

Update One-Click Catalyst flow to specify Node v24#2937
BigEth4n merged 1 commit intocanaryfrom
Update-Node-Version-for-OCC-Flow

Conversation

@BigEth4n
Copy link
Copy Markdown
Contributor

What/Why?

Catalyst has recently been updated to require Node v24 instead of the previously required v20 or v22. We're needing to update the One-Click Catalyst flow to reflect this change as currently if you try to follow the process it'll request v20 or v22 which does not work.

This update changes the versions listed in the below file to reflect v24

`You must use one of the following Node.js versions: ${prettyRequiredNodeVersions}\x1b[0m\n`,

Testing

Node 24 has been confirmed through testing to work with the latest version of Catalyst, along with being confirmed by the Catalyst engineers to be the new supported version

Migration

No files have been moved, only the listed Node version requirement has been changed for the One-Click Catalyst flow

Updated the required Node.js versions to only allow version 24.
@BigEth4n BigEth4n requested a review from a team as a code owner March 19, 2026 18:56
@vercel
Copy link
Copy Markdown

vercel Bot commented Mar 19, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
catalyst Ready Ready Preview, Comment Mar 19, 2026 6:56pm

Request Review

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Mar 19, 2026

⚠️ No Changeset found

Latest commit: e90db2c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions
Copy link
Copy Markdown
Contributor

Bundle Size Report

Comparing against baseline from 866ce20 (2026-03-19).

No bundle size changes detected.

@github-actions
Copy link
Copy Markdown
Contributor

Unlighthouse Performance Comparison — Vercel

Comparing PR preview deployment Unlighthouse scores vs production Unlighthouse scores.

Summary Score

Aggregate score across all categories as reported by Unlighthouse.

Prod Desktop Prod Mobile Preview Desktop Preview Mobile
Score 92 94 91 95

Category Scores

Category Prod Desktop Prod Mobile Preview Desktop Preview Mobile
Performance 77 91 77 93
Accessibility 95 95 95 95
Best Practices 100 100 95 100
SEO 100 100 100 100

Core Web Vitals

Metric Prod Desktop Prod Mobile Preview Desktop Preview Mobile
LCP 3.5 s 3.5 s 3.5 s 3.2 s
CLS 0 0.001 0 0
FCP 1.2 s 1.1 s 1.1 s 1.2 s
TBT 0 ms 0 ms 10 ms 0 ms
Max Potential FID 50 ms 50 ms 60 ms 40 ms
Time to Interactive 3.6 s 3.6 s 3.9 s 3.3 s

Full Unlighthouse report →

@BigEth4n BigEth4n added this pull request to the merge queue Mar 19, 2026
Merged via the queue into canary with commit 59873b1 Mar 19, 2026
21 of 23 checks passed
@BigEth4n BigEth4n deleted the Update-Node-Version-for-OCC-Flow branch March 19, 2026 19:51
chanceaclark pushed a commit that referenced this pull request Apr 27, 2026
Updated the required Node.js versions to only allow version 24.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants