Skip to content

fix(version): don't mark a stamped release build as -dirty#23

Merged
kreneskyp merged 1 commit into
mainfrom
fix/version-dirty-on-release
Jun 27, 2026
Merged

fix(version): don't mark a stamped release build as -dirty#23
kreneskyp merged 1 commit into
mainfrom
fix/version-dirty-on-release

Conversation

@kreneskyp

Copy link
Copy Markdown
Contributor

Bug (caught by dogfooding)

quoin --version printed 0.5.3-dirty for the clean published release. Cause: the release pipeline stamps package.json (0.1.3 → tag version) before prepublishOnly builds, dirtying the tree, so git describe --tags --dirty baked the -dirty suffix.

Fix

Drop --dirty. git describe --tags ignores working-tree state: HEAD-on-a-tag → bare tag (0.5.4); a build ahead of its tag → 0.5.3-2-gabc123 (drift still revealed). FR-002 updated to match.

Verified: local build on the v0.5.3 commit now bakes 0.5.3 (was 0.5.3-dirty).

🤖 Generated with Claude Code

The release pipeline stamps package.json (0.1.3 → tag version) before building,
which dirties the working tree, so `git describe --tags --dirty` baked
`X.Y.Z-dirty` into a clean published release (e.g. quoin --version printed
0.5.3-dirty). Drop --dirty: HEAD-on-tag now bakes the bare tag, while a build
ahead of its tag still shows the commits-ahead `-N-gsha` drift suffix. Update
FR-002 accordingly.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@kreneskyp
kreneskyp requested a review from a team as a code owner June 27, 2026 15:00
@kreneskyp
kreneskyp merged commit 7417a8e into main Jun 27, 2026
6 checks passed
@kreneskyp
kreneskyp deleted the fix/version-dirty-on-release branch June 27, 2026 15:02
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