Skip to content

fix(release): keep floating tags and script version current#39

Merged
NWarila merged 2 commits into
mainfrom
release-hygiene-floating-tag
Jun 4, 2026
Merged

fix(release): keep floating tags and script version current#39
NWarila merged 2 commits into
mainfrom
release-hygiene-floating-tag

Conversation

@NWarila

@NWarila NWarila commented Jun 4, 2026

Copy link
Copy Markdown
Owner

Summary

  • Stamp the released tag into .github/scripts/.version during release and backfill the marker to v1.0.6.
  • Create the immutable release tag from the stamped commit, then force-update lightweight vX and vX.Y floating tags to that release commit.
  • Add a stdlib-only release drift guard in CI for the .version marker, v1 target, and reusable workflow workflow_call triggers.

Root Cause

The floating v1 tag stopped advancing after v1.0.1, so consumers pinned to @v1 kept loading older reusable workflows even after later v1.0.x releases. The scripts version marker also drifted behind the published release, so sync state could not be trusted.

Validation

  • python tools/check_release_drift.py
  • .venv\Scripts\python.exe -m pytest tests/test_check_release_drift.py --no-cov
  • .venv\Scripts\ruff.exe check tools\check_release_drift.py tests\test_check_release_drift.py
  • .venv\Scripts\python.exe scripts\qa.py (6/6 checks, 116 tests)
  • C:\Users\hellbomb\AppData\Local\Microsoft\WinGet\Links\actionlint.exe -color=false

@NWarila NWarila marked this pull request as ready for review June 4, 2026 15:47
@NWarila NWarila merged commit e2b2d8a into main Jun 4, 2026
18 checks passed
@NWarila NWarila deleted the release-hygiene-floating-tag branch June 4, 2026 15:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant