Repository navigation
docs(releases): the 18.1 page's commit-hash caution now describes only the published tarballs - #26025
Merged
Merged
Conversation
…y the published tarballs #25804 rewrote the repository's 18.1.0 CHANGELOGs so each entry names its own commit; the published tarballs still read 3937697 and are never republished. Fixes #25806 Co-authored-by: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FH3aXUQ8ZbZARzGd17x1Nf
Contributor
Author
席位核对 — ACCEPT at
|
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
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.
Requested by Elon · project thread
What
content/docs/releases/v18/18-1.mdx, the first of the two CHANGELOG cautions. It said 260 of the 265 entries in the 18.1.0 CHANGELOGs open with3937697(the #25605 revert). Since #25804 that is true only of the published npm tarballs, which are never republished. The caution now says so, and points readers at the repository's CHANGELOGs, which name each entry's own commit. The sentence "this page cites each entry's own commit" stays.Verified before writing
npm pack @objectstack/cli@18.1.0: all 34 entries of the packed CHANGELOG's## 18.1.0section read3937697.git show origin/main:packages/cli/CHANGELOG.md: 34 entries in## 18.1.0, zero occurrences of3937697;git grep 3937697 origin/main -- 'packages/**/CHANGELOG.md'finds no file.Gates run locally
pnpm check:release-notes: OKpnpm check:release-page-status(with--self-test): OKnode scripts/check-release-section-coverage.mjs --self-testand the run: OKnode scripts/check-closed-ceremony-text.mjs: OKDocs only; publishes nothing from any released package, so
skip-changeset.Clause-②: no
Metadata-protocol: none
Fixes #25806
🤖 Generated with Claude Code
https://claude.ai/code/session_01FH3aXUQ8ZbZARzGd17x1Nf