docs: sync version references to 1.3.1, and guard them - #4
Merged
Conversation
…tale release number cannot reach a published artifact
VuongN
changed the title
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.
version.tsbumps the manifests, not the prose. Six files still said 1.3.0, includingREADME.md, which ships inside the npm tarball and renders as the package page. No tags are pushed yet, so this lands before the artifacts are cut.version:checknow sweeps those prose files too, and runs in pre-push and CI. Neither ran it before, which is why this reached a merged PR.References naming when spec 1.0 froze are deliberately unchanged.