ci: modernize test-and-release workflow to current standards#4
Merged
Conversation
- Drop Node 18.x/20.x from unit-test matrix, use [22.x, 24.x] - Use Node 24 for the deploy job - Bump actions/checkout to v7, actions/setup-node to v6, softprops/action-gh-release to v3 - Fix missing TAG env var in the npm publish step - Bump Yarn Berry from 4.10.3 to 4.17.0 and refresh yarn.lock
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Modernizes the CI/release workflow to match the current standard already rolled out in AlCalzone/jsonl-db, zwave-js/waddle and AlCalzone/node-coap-client.
[22.x, 24.x]insteadactions/checkoutto v7,actions/setup-nodeto v6,softprops/action-gh-releaseto v3TAGenv var to thenpm publishstep so pre-release tags actually get taggednextyarn.lockaccordingly