Issue
The floating major tag v1 currently points to the same commit as v1.0.0 (6878686fce27aeb6f49009173b2947a400e282b5, released Nov 2022), even though three patch releases have shipped since:
| Tag |
Commit |
runs.using |
v1 |
6878686f |
node16 |
v1.0.0 |
6878686f |
node16 |
v1.0.1 |
0181c1c9 |
(node16/20) |
v1.0.2 |
a06d172c |
node20 |
v1.0.3 |
2d89ee0b |
node24 ✅ |
The GitHub Actions recommended release management practice is to keep the major tag (v1) up to date with the latest patch release inside that line — so consumers that pin @v1 automatically get bug fixes and runtime updates.
Impact
Anyone pinning uses: allure-framework/setup-allurectl@v1 today gets v1.0.0 running on Node.js 16.
GitHub Actions runner now emits a deprecation warning for any Node 16/20 action and has announced removal dates (changelog):
- 2026-06-16 — runner forces Node 24 by default
- 2026-09-16 — Node 20 removed from the runner (Node 16 already deprecated)
After 2026-09-16, all consumers pinning @v1 will break unless they switch to @v1.0.3 (or a future @v2) — which is awkward because they explicitly chose to track the floating major tag for upgrades they don't have to think about.
Dependabot also can't help here: it sees @v1 as the latest major and doesn't propose v1.0.3 updates because semantically the version a consumer pinned (v1) is still resolvable. We see this in practice across many repositories we maintain at https://github.com/dodobrands and https://github.com/dodopizza.
Suggested fix
Re-create the v1 tag on 2d89ee0b7ba2f59dbe9849b6df5763cab78e14db (current v1.0.3):
git tag -f v1 v1.0.3
git push origin -f v1
Optionally automate this for future releases (e.g. via actions/publish-action or a small workflow that moves the major tag on every published release).
Happy to send a PR with such an automation workflow if it would help. Thanks!
Issue
The floating major tag
v1currently points to the same commit asv1.0.0(6878686fce27aeb6f49009173b2947a400e282b5, released Nov 2022), even though three patch releases have shipped since:runs.usingv16878686fnode16v1.0.06878686fnode16v1.0.10181c1c9v1.0.2a06d172cnode20v1.0.32d89ee0bnode24✅The GitHub Actions recommended release management practice is to keep the major tag (
v1) up to date with the latest patch release inside that line — so consumers that pin@v1automatically get bug fixes and runtime updates.Impact
Anyone pinning
uses: allure-framework/setup-allurectl@v1today getsv1.0.0running on Node.js 16.GitHub Actions runner now emits a deprecation warning for any Node 16/20 action and has announced removal dates (changelog):
After 2026-09-16, all consumers pinning
@v1will break unless they switch to@v1.0.3(or a future@v2) — which is awkward because they explicitly chose to track the floating major tag for upgrades they don't have to think about.Dependabot also can't help here: it sees
@v1as the latest major and doesn't proposev1.0.3updates because semantically the version a consumer pinned (v1) is still resolvable. We see this in practice across many repositories we maintain at https://github.com/dodobrands and https://github.com/dodopizza.Suggested fix
Re-create the
v1tag on2d89ee0b7ba2f59dbe9849b6df5763cab78e14db(currentv1.0.3):Optionally automate this for future releases (e.g. via
actions/publish-actionor a small workflow that moves the major tag on every published release).Happy to send a PR with such an automation workflow if it would help. Thanks!