renovate

mirror of https://github.com/renovatebot/renovate.git synced 2026-10-25 06:51:11 +00:00

Files

T

Jamie Tanna 673fb8e7a9 fix(versioning/github-actions): allow v1.2 to be treated as a version (#42761 )

When using `docker` versioning, we correctly treat a `v1.2` -> `v1.3`
version update as valid.

However, when using the previous implementation of `github-actions`'
versioning, we would silently ignore them, filtering them in
`filterValidVersions`.

This leads to cases where a `v1.2` would be upgraded to `v1.3.0`, which
wasn't correct.

Co-authored-by: Claude Sonnet 4.6 <jamie.tanna+claude-code@mend.io>

2026-04-20 09:21:32 +00:00

index.spec.ts

fix(versioning/github-actions): allow v1.2 to be treated as a version (#42761 )

2026-04-20 09:21:32 +00:00

index.ts

fix(versioning/github-actions): allow v1.2 to be treated as a version (#42761 )

2026-04-20 09:21:32 +00:00

readme.md

…

readme.md

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