docs(changelog): record the action-gh-release v3.0.2 bump (#101) - #134
Merged
Merged
Conversation
#101 moved softprops/action-gh-release to v3.0.2 and shipped in v0.10.0 with no changelog entry. That left the v0.9.0 note about v3.0.1 (#94) as the file's last word on the pin, understating what actually ships — the tree has carried 3d0d9888… (v3.0.2) since. Entered retrospectively into the v0.10.0 Changed section, where it belongs, alongside a note that it is retrospective so the gap is visible rather than papered over. Matches the style of the #94 entry one release earlier. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the repository changelog to retrospectively document the previously-unrecorded bump of softprops/action-gh-release to v3.0.2 (SHA 3d0d9888cb7fd7b750713d6e236d1fcb99157228) that shipped with v0.10.0, closing a documentation gap.
Changes:
- Add a v0.10.0 “Changed” entry noting the
softprops/action-gh-releasev3.0.2 SHA pin forpublish-gh-pages. - Explicitly mark the entry as recorded retrospectively.
"this shipped in v0.10.0 with no changelog entry" reads as self-refuting once the line is itself a v0.10.0 changelog entry. "at the time" fixes that, and "this" → "it" removes the ambiguity between the bump and the entry that probably invited the misreading. Keeping "Recorded retrospectively": that phrase is the point of the entry, since it makes visible that a dependency bump landed without a record. A silently backfilled line would hide it. Raised by Copilot on #134. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Fills a gap found while tidying up after the v0.11.1 release.
#101 moved
softprops/action-gh-releaseto v3.0.2 and shipped in v0.10.0 with no changelog entry. The file's last word on that pin was therefore the v0.9.0 line recording v3.0.1 (#94), while the tree has carried3d0d9888cb7fd7b750713d6e236d1fcb99157228— v3.0.2 — ever since. Confirmed against the upstream tag list rather than reading the pin comment: that SHA resolves tov3.0.2.The entry goes into the v0.10.0 Changed section where it belongs, in the same style as the #94 entry one release earlier, and says explicitly that it is recorded retrospectively — a silently backfilled entry would hide the fact that a dependency bump can land here without one.
Worth noting for its own sake: this is the second thing this week that drifted because a bump landed without a record. Not worth process changes on one instance, but if it recurs, requiring a changelog line on dependency PRs would be the fix.
🤖 Generated with Claude Code