Repository navigation
[Snyk] Prefer a stable release as the fix version for a stable version - #125
Merged
Merged
Conversation
irskep
force-pushed
the
fix-version-skips-prereleases
branch
from
October 16, 2026 17:11
278f3df to
68649ca
Compare
Snyk lists the canary that first carried a fix next to the release that followed. `lowestFixVersion` took the lowest, so a stable version could be asked to move to a canary, and the due date then counted from a release that was not the one asked for. A stable version now takes a stable fix when one fixes everything, and a prerelease only when nothing else does. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
irskep
force-pushed
the
fix-version-skips-prereleases
branch
from
October 19, 2026 16:45
68649ca to
f7349d4
Compare
srubin
approved these changes
Oct 19, 2026
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.
Snyk lists the canary that first carried a fix next to the release that followed, for example
15.6.0-canary.61, 16.1.1-canary.16, 16.1.5.lowestFixVersiontook the lowest of them, so a stable version could be asked to move to a canary. The canary is not in the versions between current and latest, so the due date then counted from a different release than the title asked for.A stable version now takes a stable fix when one fixes everything, and a prerelease only when nothing else does. A version that is itself a prerelease can still move to a later one.
🤖 Generated with Claude Code