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

workflows: update and pin node versions #717

Closed
wants to merge 3 commits into from
Closed

workflows: update and pin node versions #717

wants to merge 3 commits into from

Conversation

gurgunday
Copy link
Member

No description provided.

@mcollina
Copy link
Member

windows on node 22 must be skipped for now

@@ -17,7 +17,8 @@ on:

jobs:
test:
uses: fastify/workflows/.github/workflows/plugins-ci.yml@v4.1.0
uses: fastify/workflows/.github/workflows/plugins-ci.yml@v4.2.1
Copy link
Member

Choose a reason for hiding this comment

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

I believe we can release v4, because the node version is now configurable.

Copy link
Member Author

Choose a reason for hiding this comment

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

We’d have to configure every plugin manually, so not sure

I’m pinning libraries right now as they are fastify independent

Copy link
Member

Choose a reason for hiding this comment

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

No, it has default inside the workflow.
It only need to configure if you do not use the default.

That means we can even use v4 for the current main branch.
It is not limited to the next branch.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes it does, but the default tests for 18, 20, 21

main branches still test for 14, 16, so they would all need manual modification, no?

Copy link
Member Author

Choose a reason for hiding this comment

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

But yeah not saying we cannot do it

Copy link
Member

Choose a reason for hiding this comment

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

Eventually, we need to update all of them back to v4 tag.
We can do this earlier if we release.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah actually could be good as even next versions currently have hardcoded versions... which in not ideal

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.

6 participants