ci: add support to test release candidates#6103
Merged
mcollina merged 1 commit intofastify:mainfrom May 11, 2025
Merged
Conversation
metcoder95
approved these changes
May 5, 2025
Member
metcoder95
left a comment
There was a problem hiding this comment.
It would be also interesting to explore have these as a cron-job to attempt detect possible regressions/issues
Eomm
approved these changes
May 11, 2025
jean-michelet
pushed a commit
to jean-michelet/fastify
that referenced
this pull request
May 13, 2025
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This is just an idea, but I think it would be interesting to be able to test Node.js release candidates, specially for semver-major versions