docs(prompt-authoring): prevent a second bump from a version-bump FAIL - #88
Merged
azevedo merged 1 commit intoAug 11, 2026
Conversation
Discovered while shipping the 5e/5f receipt fix: committing a prompt-surface change on a branch whose bump landed three commits earlier turns version-bump red locally, and the obvious "fix" is a second bump — which burns an unpublished version number and makes consumers skip it. The check compares HEAD~1..HEAD, one commit. On a branch that is the previous branch commit; in CI on a pull_request it is the base tip, because GitHub checks out an ephemeral merge commit whose first parent is the base — so the same comparison spans the PR's cumulative diff and one bump satisfies it. Records the rule, the mechanism that makes local and CI disagree, and the confirmation step (compare the cumulative diff against the base) so the red build is read rather than appeased.
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
2 participants
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.
Risk: low — doc-only; no runtime surface changed
A
version-bumpFAIL at a branch HEAD read as a defect, and the obvious fix — add another bump — burns an unpublished version number consumers skip. The doc now explains why the check'sHEAD~1..HEADwindow fails locally on almost every prompt-surface commit yet passes on a PR's cumulative diff.Proof: pending — add tests / QA notes / screenshots before merge