fix: restore the 1.1.0 changelog to what actually shipped - #17
Merged
Conversation
The release pull request merged 104 seconds before the fix that would have corrected it, so main carries a 1.1.0 section of 98 entries reaching back into pre-public history — "added support for storing dark mode", "basic layout styles" — with several listed twice, once for the branch commit and once for the merge. Replaced with the six commits actually made since 1.0.0, grouped by the headings release-please would have used, so the next generated entry sits on top of something the same shape. Also drops two links to a `v1.0.0` tag that does not exist and never will: 1.0.0 was a version in the manifest, and the first release cut from this repository is 1.1.0. The heading says so rather than pointing at a 404. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
| Commit | Scanned at | New | Resolved | Net |
|---|---|---|---|---|
837d2b6 < |
2026-08-17 01:54 UTC | 0 | 0 | 0 |
Last scanned: 837d2b6 · 2026-08-17 01:54 UTC
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.
CHANGELOG.mdonmaincurrently has a 1.1.0 section with 98 entries, most of them pre-public internal history.#15 merged at
01:37:38Z. #16 — the fix that anchors release-please — merged at01:39:22Z. 104 seconds too late, so the release pull request wrote its unanchored changelog before the anchor existed.Several entries appear twice, once for the branch commit and once for the merge commit.
What 1.1.0 actually contains
Six commits since 1.0.0, grouped by the headings release-please itself would have used, so the next generated entry sits on top of something the same shape:
Added — the Claude skill, local releases without a GitHub App, artifacts attachable to a hand-cut tag
Fixed — GHSA-mw96-cpmx-2vgc, and anchoring release-please to the 1.0.0 commit
Documentation — how to install the skill
Two dead links removed
Both the 1.0.0 heading and its link reference pointed at
releases/tag/v1.0.0. That tag does not exist and never will — 1.0.0 was a version in the manifest, not a release, and the first tag cut from this repository is v1.1.0. The heading now says that plainly instead of linking to a 404.Note on the process
Nothing has been tagged yet, which is why no release is visible:
release:tagis the step that creates it, and it is still pending. Merging this first means the tag lands on a truthful changelog.🤖 Generated with Claude Code