mirror of
https://github.com/renovatebot/renovate.git
synced 2026-10-25 06:51:11 +00:00
b81bf5dade
* fix(versioning/github-actions): don't parse `allowedVersion`-style ranges as a range As noted in #42824, when using a range for `allowedVersion`, changes to how ranges are parsed with `semver.coerce` led to incorrectly matching this as a version that would like to be updated to. We can guard this by making sure a SemVer style version number is used. Co-authored-by: Claude Sonnet 4.6 <jamie.tanna+claude-code@mend.io> * perf(versioning/github-actions): create constants for regexes Co-authored-by: Claude Sonnet 4.6 <jamie.tanna+claude-code@mend.io> * test: skip coverage Co-authored-by: Claude Sonnet 4.6 <jamie.tanna+claude-code@mend.io> * fixup Co-authored-by: Michael Kriese <michael.kriese@visualon.de> --------- Co-authored-by: Claude Sonnet 4.6 <jamie.tanna+claude-code@mend.io> Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
Versioning specific to GitHub Actions' usage of Semantic Versioning, for mutable and immutable tags.
The "shortest" tag will be used where possible - if you are previously using v7, and there is an upgrade to v7.5.3, v7 will be used.
Immutable Tags
When using Immutable Releases for GitHub Tags, it is required to use explicit SemVer major.minor.patch versions.
If you have previously used an unpinned version, such as @v7, Renovate will migrate you on the next update, such as:
- uses: astral-sh/setup-uv@v7
+ uses: astral-sh/setup-uv@v8.1.0