chore(ci): Update .nvmrc to node 20#32
Merged
brian-smith-tcril merged 1 commit intoopenedx:masterfrom Jun 6, 2025
Merged
Conversation
dcoa
pushed a commit
to fccn/brand-nau
that referenced
this pull request
Nov 27, 2025
sandroscosta
pushed a commit
to fccn/brand-nau
that referenced
this pull request
Dec 4, 2025
MohamedAhmedG
pushed a commit
to zeit-labs/eduba-brand-openedx
that referenced
this pull request
Jan 12, 2026
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
2 participants
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.
Noticed the release workflow failed https://github.com/openedx/brand-openedx/actions/runs/15495997755/job/43632751864 because it was using node 18 and a version of
semantic-releasethat isn't compatible with node 18. We've worked around this in the past by specifying a version ofsemantic-releasethat is compatible with node 18, but I decided updating the.nvmrcto use node 20 makes more sense because we should be using node 20 here anyways.I also verified that running
npm ci,npm run buildworks with node 20. I also tested runningnpm installand saw no changes to the package lock.