docs-check: pin v0.1.1, and stop claiming v0.1.0 is the listed release - #42
Merged
Conversation
Supersedes dependabot #22, which has been open 27 days and went CONFLICTING because release.yml and scheduled-ci.yml both changed under it today. It also predates verify-wheel.yml, so merging it as-is would have left one workflow on v6 and produced a second dependabot PR immediately. 12 occurrences across 7 files. v7.0.0 released 2026-07-20.
The comment said v0.1.0 is 'the same one a Marketplace listing is made from'. That stopped being true today: the listing was published from v0.1.1, because v0.1.0's action.yml carries name 'docproof' and GitHub refuses a name matching an existing account. So this gate was pinned to a release that can no longer be listed while claiming it was the listed one - a stale statement inside the gate whose job is catching stale statements. Measured both ways before bumping rather than assumed: v0.1.0 and v0.1.1 each report 112 claims checked and nothing contradicted on this tree, run from a worktree at each tag. So this is hygiene, not a fix, and the commit says so.
Jules ReviewCOVERAGE: a759ca5 8 files SummaryThis PR bumps VerdictVERDICT: approve This review never edits code or force-blocks a merge. No blocking issues were found, so this PR was auto-approved. |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
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
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.
This workflow was pinned to
melbinjp/docproof@v0.1.0and said, in its own comment, thatv0.1.0 is "the release a Marketplace listing is made from."
That stopped being true today. The listing went up from v0.1.1, because v0.1.0's
action.ymlcarriesname: 'docproof'and GitHub refuses a name matching an existingaccount - a User
docproofexists and is not ours. So this repository was pinned to arelease that can no longer be listed at all, while its comment claimed it was the listed one.
A stale statement inside the gate whose entire job is catching stale statements. Worth fixing
for that reason alone.
Measured before bumping, both directions
v0.1.0v0.1.1Identical, so this is hygiene and not a fix. The seven commits between the tags are
precision rules derived from other repositories plus the name change; none of them alters
what this one reports. Claiming a win here would be inventing one.
Run from a worktree at each tag rather than reasoned about, because the whole argument for
pinning is that you cannot tell the checker from the code by reading.
Why bump at all, then
The pin is the thing that decides which checker runs when this repository's documentation
does eventually drift. Leaving it on a release that GitHub will not list means the gate and
the published tool diverge quietly from here on, and the first time they disagree nobody will
know which one was right.