Repository navigation
fix(release): ignore generated GoReleaser output - #193
Merged
antoinetoussaint-byte merged 1 commit intoOct 28, 2026
Merged
Conversation
antoinetoussaint-byte
requested a review
from AntoineToussaint
as a code owner
October 28, 2026 22:48
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.
GoReleaser writes root dist/ metadata before compiling. Because that output was unignored, Go included it in the VCS dirty state and the published v0.0.170 binaries reported vcs.modified=true and +dirty.
Add root-anchored /dist/ to .gitignore and document the reason and future artifact check in .claude/skills/release-agent/SKILL.md. This is a fix at the repository release owner: it reuses Git output exclusions and keeps normal Go VCS stamping. No new release mechanism or stamping bypass is introduced. Existing v0.0.170 artifacts and Blue image attribution remain unchanged.
Validation: focused agent-context/skill-contract tests passed; git diff --check passed. The retained Git reversal probe shows generated root dist is visible without the rule and excluded with it, while an unrelated untracked change stays visible. The applied rule also leaves unrelated nested paths unmatched. All five hosted jobs passed on exact d3b187d in run40782794273: build, test, Sync, effective-inputs conformance and manifest guard. No local engine, publisher, retag or new-version build was performed. Actual next-release metadata remains a future release verification, not a result claimed here.
Overlap checked against fresh main befe1c1 and open PR181 (nginx), PR182 (Actions), PR184 (npm); none covers this correction. This successor uses the existing PR183 owner workspace and preserves its history.