Fix Renovate scala-version customManager: pin versioningTemplate to semver - #27
Merged
Merged
Conversation
…emver
Root cause of the customManager never proposing a bump despite newer
scala/scala3 tags existing (3.9.0-RC5, -RC6): with no versioningTemplate
set, Renovate falls back to its default semver-coerced versioning, which
strips the prerelease suffix ("3.9.0-RC4" -> "3.9.0", "3.9.0-RC6" ->
"3.9.0"). Both values coerce to the same version, so Renovate saw no
difference and never proposed an update — confirmed via the Dependency
Dashboard, which showed "scala3 3.9.0-RC4" with no available-updates
annotation even though newer tags clearly exist.
Setting versioningTemplate: semver (strict, not coerced) preserves the
prerelease distinction so RC-to-RC comparisons work correctly.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.
Root cause of the scala-version customManager never proposing a bump despite newer
scala/scala3tags existing (3.9.0-RC5,-RC6): with noversioningTemplateset, Renovate falls back to its defaultsemver-coercedversioning, which strips the prerelease suffix ("3.9.0-RC4"→"3.9.0","3.9.0-RC6"→"3.9.0"). Both values coerce to the same version, so Renovate saw no difference and never proposed an update — confirmed via the Dependency Dashboard, which showedscala3 3.9.0-RC4with no available-updates annotation even though newer tags clearly exist.Setting
versioningTemplate: semver(strict, not coerced) preserves the prerelease distinction so RC-to-RC comparisons work correctly.🤖 Generated with Claude Code