Skip to content

Conversation

@marcdumais-work
Copy link
Contributor

Add node 20,22 for build and tests (keep 18 for now). Use 20 for publish and license check.

What it does

Prepare for node.js 18 EoL and our transition to using node 20 as default.

  • start using node 20 for jobs like linting, publishing and license check
  • Add Node 20 and node 22 to the matrix for "build and test" job
  • (for now) Keep node 18 as part of the "matrix" for "build and test job". We can remove it once officially EoL

How to test

Confirm CI still passes.

Follow-ups

Review checklist

  • As an author, I have thoroughly tested my changes and carefully followed the instructions in this template

@marcdumais-work
Copy link
Contributor Author

IP Ticket opened (unrelated to this PR I think):

[main] INFO A review is required for npm/npmjs/-/ts-jest/29.2.5.
[main] INFO A review request was created https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/19364 .

@marcdumais-work marcdumais-work changed the title [CI][workflows] Use node 20, 22 in workflows [CI][workflows] Use node 20 by default Feb 7, 2025
@marcdumais-work marcdumais-work marked this pull request as ready for review February 7, 2025 21:14
@marcdumais-work marcdumais-work changed the title [CI][workflows] Use node 20 by default [CI][workflows] Use node 20 by default, align GitHub workflows Feb 10, 2025
- published
- published
schedule:
- cron: '0 4 * * *' # Runs every day at 4am: https://docs.github.com/en/actions/reference/events-that-trigger-workflows#scheduled-events-schedule
Copy link
Contributor

Choose a reason for hiding this comment

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

Why was the cron job added?

Copy link
Contributor Author

@marcdumais-work marcdumais-work Feb 10, 2025

Choose a reason for hiding this comment

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

It's a test for a theory. In this repo we have the license check on a cron job but recently the nightly license check started to fail, and the repo's main page was still reflecting a successful state (i.e. the state of the last complete CI run, when the last PR was merged). I'm hoping what with both workflows triggered nightly, the status of an eventually failed license check on master will show on the main project page.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I removed the new cron entry

Prepare for node.js 18 EoL and transition to node 20 as default

- start using node 20 for jobs like linting, publishing and license
  check
- Add Node 20 and node 22 to the matrix for "build and test" job
- (for now) Keep node 18 as part of the "matrix" for "build and test
  job". We can remove it once officially EoL

The plan is to remove node 18 soon, when it's officially EoL.

Signed-off-by: Marc Dumais <[email protected]>
Copy link
Contributor

@bhufmann bhufmann left a comment

Choose a reason for hiding this comment

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

Looks good to me. Thanks!

@marcdumais-work
Copy link
Contributor Author

Thanks for the review!

@marcdumais-work marcdumais-work merged commit d3f9662 into master Feb 10, 2025
7 checks passed
@marcdumais-work marcdumais-work deleted the prepare-node-20 branch February 10, 2025 16:29
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