Repository navigation
chore: upgrade Node.js to 24 - #79
Open
rahulkanneri-2u wants to merge 1 commit into
Open
rahulkanneri-2u wants to merge 1 commit into
rahulkanneri-2u wants to merge 1 commit into
Conversation
rahulkanneri-2u
force-pushed
the
chore/upgrade-node-24
branch
from
October 6, 2026 10:39
f17eb26 to
1e2da46
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Upgrade
course-discoveryto use Node.js 24 for frontend asset builds.This adds a repository-level Node version declaration and a dedicated CI job to validate the production frontend asset build on Node 24.
Changes
.nvmrcwith Node.js 24.frontend_assetsCI job that:.nvmrc;The build retains
NODE_OPTIONS=--openssl-legacy-provider, matching the currentpublic-dockerfilesNode 24 build configuration. This is needed for the existing legacy loader/MD4 hashing behavior and should be removed in a future dependency-modernization follow-up.Testing
Validated locally with Node.js 24: