docs(release-notes): retitle unreleased v6.4.0 notes as v6.4.1 - #2336
Merged
Merged
Conversation
v6.4.0 was prepared but never shipped (release PR #2331 closed unmerged, no tag). The next release is v6.4.1. Rename the section and open it with a note saying v6.4.0 never shipped and that v6.4.1 holds back the proving-it-works-with-a-movie skill for cleanup and robustness work before it returns. The note replaces the revert paragraph added in #2335. Version bumps are left for the release step. Claude-Session: https://claude.ai/code/session_01PRUnVUm4g4EcP9eNjAiT2B
This was referenced Sep 18, 2026
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.
Who is submitting this PR? (required)
What problem are you trying to solve?
The top section of RELEASE-NOTES.md on
devis## v6.4.0 (2026-09-18), but v6.4.0 never shipped: the release PR #2331 tomainwas closed unmerged and there is no v6.4.0 tag.mainis still v6.3.0. After #2335 reverted theproving-it-works-with-a-movieimport (#2214), the next release will be v6.4.1. Without this change, the notes describe a v6.4.0 that users never got, and the reverted skill reads as permanently dropped when it is coming back.What does this PR change?
Renames the section to
## v6.4.1 (2026-09-18)and opens it with a short note: v6.4.0 was never shipped, v6.4.1 is the first release with these changes, and it holds back the movie skill for cleanup and robustness work before it returns in a later release. That note replaces the revert paragraph #2335 added. The rest of the section is unchanged. No version bumps; that is a separate release step.Is this change appropriate for the core library?
Yes. It is the project's own release notes.
What alternatives did you consider?
Keeping a
## v6.4.0heading marked unreleased alongside a new v6.4.1 section. That would duplicate the full changelog under two versions for one shipped release. Keeping #2335's revert paragraph next to the new note would say the same thing twice, and its wording implied the skill was gone for good.Does this PR contain multiple unrelated changes?
No. One file, one section.
Existing PRs
Environment tested
Documentation only; nothing to run. I checked that the v6.4.1 section no longer describes the movie skill as shipping; the only mention is the new note.
New harness support (required if this PR adds a new harness)
Not applicable. This PR adds no harness.
Evaluation
devto say v6.4.0 was never shipped and that v6.4.1 ships this work and temporarily holds back the movie skill.Rigor
Human review
Left unchecked on purpose: Jesse asked for this PR and reviews the full diff here on the PR.
https://claude.ai/code/session_01PRUnVUm4g4EcP9eNjAiT2B