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

[CI][workflows] Use node 20 by default, align GitHub workflows #304

Merged
merged 1 commit into from
Feb 10, 2025

Conversation

marcdumais-work
Copy link
Contributor

@marcdumais-work marcdumais-work commented Feb 6, 2025

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 marcdumais-work force-pushed the prepare-node-20 branch 7 times, most recently from 7ffa566 to b461dc0 Compare February 7, 2025 21:11
@marcdumais-work marcdumais-work marked this pull request as ready for review February 7, 2025 21:14
@@ -119,14 +120,14 @@ jobs:

publish-vs-marketplace:
# https://marketplace.visualstudio.com/
name: Publish extension to Visual Studio Marketplace
name: Publish extension to Visual Studio Marketplace (${{ matrix.os }}
Copy link
Collaborator

Choose a reason for hiding this comment

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

You might have the issue here too

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good catch\

@@ -86,14 +87,14 @@ jobs:

publish-oxsv:
# https://open-vsx.org/
name: Publish extension to public Open VSX Registry
name: Publish extension to public Open VSX Registry (${{ matrix.os }})
Copy link
Collaborator

Choose a reason for hiding this comment

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

I see matrix.os printed instead of the actual value. Maybe it can't be resolved when it's skipped. You could hard code it or just omit as it was before.

image

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The reason I wanted to include it is that when do not, then automatically all matrix variable values are printed-out, without their corresponding "key", which looks strange. But that does not actually happen for these release workflows, that are triggered by an action vs directly by a PR push.

So I'll remove the change for these and we should be good

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 <marc.dumais@ericsson.com>
@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
Copy link
Collaborator

@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 a lot.

@marcdumais-work
Copy link
Contributor Author

Thanks for the review!

@marcdumais-work marcdumais-work merged commit 50384e8 into master Feb 10, 2025
8 checks passed
@marcdumais-work marcdumais-work deleted the prepare-node-20 branch February 10, 2025 15:21
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