Pin published docs to alpha.112#130
Merged
Merged
Conversation
The v0.1.0-alpha.112 release did not carry the post-release version bump, so the docs quickstart, tracing guide, index and README still told users to depend on alpha.111. Release-Notes: Internal: Documentation dependency pins now reference v0.1.0-alpha.112.
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.
v0.1.0-alpha.112shipped without its post-release version bump, so the quickstart, tracing guide, docs index and README still instruct users to depend on alpha.111.docs lint: okafter the bump.This is currently blocking every other open PR. The docs lint gate works correctly — it compares the pinned version against the latest release tag.
mainwent green at648d2324because that merged before alpha.112 existed, when the pin still matched. The moment alpha.112 was tagged, the pin went stale andTest docs + build cachebegan failing on all subsequent PRs (#128 and #129 are both red on exactly this).So the real gap is process, not tooling: releasing does not bump the pin, so every release red-lines all open PRs until a human notices and files this.
docs/PUBLISHING.mddocuments the manual step; nothing enforces or automates it. Follow-up: either have the release workflow open this bump automatically, or gate the release on it.