chore(specgit): pin the acceptance workflow's specgit CLI to ^0.5.0 - #367
Merged
Conversation
npm install -g specgit installs whatever is latest at run time; the CLI releases multiple times a day, so an unnoticed upstream change could flip CI acceptance verdicts repo-wide. Caret floor keeps patch/minor fixes while making the installed floor reproducible. Also restores this repo's bun/npm harness adaptation that a local 'specgit issue' run (0.5.0) had overwritten with the pnpm template. Closes#366
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes#366
What
specgit@^0.5.0instead of unpinnedspecgit. Rationale: the CLI ships multiple releases a day (0.2.0→0.5.0 within one day); an unpinned install lets an unnoticed upstream change flip CI acceptance verdicts repo-wide with no change in this repo. A caret floor follows the CLI's evolution (per the maintainer's direction to track latest) while keeping each run reproducible.npm i -g+ minimal policy parse) that a localspecgit issuerun under 0.5.0 had overwritten with the pnpm template — 0.5.0 regenerates the harness onissue, so the repo adaptation is now treated as a delivery-reviewed artifact: regenerated content gets reviewed like code and restored in the same PR.Verification