Skip to content

upgrade to Node.js 24#868

Open
panish16 wants to merge 1 commit intobcgov:mainfrom
panish16:32835-nodejs
Open

upgrade to Node.js 24#868
panish16 wants to merge 1 commit intobcgov:mainfrom
panish16:32835-nodejs

Conversation

@panish16
Copy link

Issue #: https://app.zenhub.com/workspaces/sre-team-board-654d163c6817d80016102d9a/issues/gh/bcgov/entity/32835

Description of changes:
Update engines field in package.json to require Node.js >= 24.
Update GitHub Actions CI/CD workflows to use Node 24.
Align with modern runtime standards and ensure pipeline stability.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the bcrs-entities-create-ui license (Apache 2.0).

Copy link
Collaborator

@stevenc987 stevenc987 left a comment

Choose a reason for hiding this comment

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

The latest package version is 5.8.11 on repo. Please update the version number

@severinbeauvais
Copy link
Collaborator

The latest package version is 5.8.11 on repo. Please update the version number

Anish, please rebase and then bump up the app version. I recommend using version 5.9.0.

patchedDependencies:
sbc-common-components@3.0.15-c:
hash: dbxsbs7nnq5sxpyu75cpekwise
hash: 04ee617a4ac7ced8e6cfab349eeccdc740e5a5be3543ee92d05d0966a39046be
Copy link
Collaborator

Choose a reason for hiding this comment

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

This change concerns me. It may be that you have to re-patch this package (or this may be a Node 24 thing, I dunno).

If you have to re-patch, look up how to do it and look at the current patch (as per the path at the bottom of the package.json file).

Otherwise, you might be able to get away with simply leaving THIS file unchanged (ie, uncommit it).

You'll have to test if that works either way.

@severinbeauvais
Copy link
Collaborator

@panish16 You have two outstanding comments above before this PR can be merged.

Also, please chase down the other reviewers for this code change -- another team (not Entities) owns this repo. Thanks.

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