docs: fix stale v1.0.0 references after the 1.0.1 release#40
Merged
Conversation
- README 'current release' bullet was hardcoded to v1.0.0 — de-hardcode it to point at the dynamic Release badge so it never goes stale again. - CHANGELOG link-reference footer still pointed [Unreleased] at v1.0.0 and had no [1.0.1] target (leaving the new ## [1.0.1] heading a dead link) — repoint [Unreleased] to v1.0.1...HEAD and add the [1.0.1] tag. - release.yml workflow_dispatch example: generic v1.2.3, not v1.0.0. - DEVELOPMENT.md release checklist: add the CHANGELOG-footer + coverage version-line steps that were missed this release, and note the README version is now dynamic. Docs-only; the published v1.0.1 release/tag is unaffected. Co-Authored-By: Claude Opus 4.8 (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.
Post-release cleanup of v1.0.0 references the 1.0.1 release (#39) didn't touch. Docs-only — the published v1.0.1 tag/release is unaffected.
Fixes
[Unreleased]: …compare/v1.0.0…HEADand no[1.0.1]target, which left the## [1.0.1]heading as a dead link. Repointed[Unreleased]tov1.0.1…HEADand added[1.0.1]: …/releases/tag/v1.0.1.workflow_dispatchexample tag is now generic (v1.2.3) instead ofv1.0.0.coverage.md's**Version:**line) and noted the README version is now dynamic.Why these were missed
The release checklist (step 4) covered moving the
[Unreleased]heading but not the footer link definitions or the README/coverage version lines — so they drifted. The DEVELOPMENT.md change closes that gap for next time.🤖 Generated with Claude Code