Skip to content
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.

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

CRDCDH-2396 Upgrade Node to v22 #620

Open
wants to merge 5 commits into
base: 3.3.0
Choose a base branch
from
Open

CRDCDH-2396 Upgrade Node to v22 #620

wants to merge 5 commits into from

Conversation

amattu2
Copy link
Member

@amattu2 amattu2 commented Feb 7, 2025

Overview

This PR upgrades our local/actions Node.js version to v22 to address security vulnerabilities and maintain consistency with the backend services. Additionally:

  • It specifies the required node and npm versions in our package.json file
  • It strictly enforces the versions when running NPM commands

Note

To upgrade and set the new default (if using nvm):

nvm install 22
nvm alias default 22
nvm use

Change Details (Specifics)

N/A

Related Ticket(s)

CRDCDH-2396

@amattu2 amattu2 added the 🚧 Do Not Merge This PR is not ready for merging label Feb 7, 2025
@amattu2 amattu2 added this to the 3.2.0 (PMVP-M3) milestone Feb 7, 2025
@amattu2

This comment was marked as outdated.

@coveralls
Copy link
Collaborator

coveralls commented Feb 7, 2025

Pull Request Test Coverage Report for Build 13722816295

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 60.271%

Totals Coverage Status
Change from base Build 13701700680: 0.0%
Covered Lines: 4372
Relevant Lines: 6835

💛 - Coveralls

@amattu2 amattu2 modified the milestones: 3.2.0 (PMVP-M3), 3.3.0 Feb 19, 2025
@amattu2 amattu2 changed the title Upgrade Node to v22 CRDCDH-2396 Upgrade Node to v22 Feb 19, 2025
@amattu2 amattu2 changed the base branch from 3.2.0 to 3.3.0 March 3, 2025 14:36
@amattu2 amattu2 removed the 🚧 Do Not Merge This PR is not ready for merging label Mar 5, 2025
@amattu2 amattu2 marked this pull request as ready for review March 5, 2025 17:13
@amattu2 amattu2 requested a review from Alejandro-Vega March 5, 2025 17:13
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.

2 participants