Repository navigation
Release v1.9.6: make the committed cover snapshot deterministic - #67
Merged
Merged
Conversation
As shipped in 1.9.5 the snapshot carried the build stamp, whose commit hash and timestamp change on every run. Every build therefore dirtied docs/cover.html even when nothing about the page had changed — noise in git status forever, and a permanent failure of this skill's own clean-tree gate before deploy. The stamp is now stripped from the committed copy only; the published dist still carries it. Two consecutive builds from unchanged source produce identical bytes, so the snapshot moves only when the page or version does. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bug in what 1.9.5 just shipped
The
LOCAL_COPYsnapshot added in 1.9.5 inherited the build stamp:<!-- repo:ef240a8 built:2026-08-13T03:54:40Z -->Both fields change on every run. So every
build-cover-dist.shinvocation dirtieddocs/cover.html, even with the page and version untouched — caught immediately when rebuilding at the tagged commit produced a modified file with no real change.That is not cosmetic. The skill's Gate 4 requires a clean working tree before deploy, and the build itself would have violated it every single time. A committed artifact has to be deterministic or it cannot be committed meaningfully.
Fix
Strip the stamp from the committed copy only. The published dist keeps it — provenance belongs on the deployed page, where nothing diffs it.
Verified
The snapshot now moves only when the page or the version does.
🤖 Generated with Claude Code