Repository navigation
chore: keep Node and Deno major versions floating in CI - #388
Merged
Merged
Conversation
rexxars
changed the title
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
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.
The CI jobs already accept any Node 24.x and Deno 2.x release. #385 and #384 would have pinned them to 24.22.2 and 2.9.8, so we'd need another PR for the next patch.
Skip minor and patch updates for major-only Node and Deno selectors in GitHub Actions inputs. Major upgrades still go through the dependency dashboard, and explicitly pinned versions can still get patch updates.