Changelog: canonical tag-based links for v1.2.0 - #19
Merged
Conversation
The v1.2.0 release is tagged, so repoint the two footer links that used the dfda97a commit anchor at the canonical tag compares: - [1.2.0]: v1.1.0...v1.2.0 - [Unreleased]: v1.2.0...HEAD [1.1.0] and [1.0.0] are unchanged. Both updated links resolve against existing tags, so the Markdown-link CI job stays green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01241uUFYvyppDmAq8ywxvGF
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.
Summary
Now that the
v1.2.0release is tagged (tagv1.2.0→c333d2b), repoint the twoCHANGELOG.mdfooter links that used the temporarydfda97acommit anchor at thecanonical tag compares:
[1.2.0]→compare/v1.1.0...v1.2.0[Unreleased]→compare/v1.2.0...HEAD[1.1.0]and[1.0.0]are left untouched. Both updated links resolve againstexisting tags, so the Markdown-link CI job stays green.
Type of change
Safety impact
None — this change cannot affect risk gates, sizing, or fund safety. It only edits
two reference-style Markdown link definitions in
CHANGELOG.md.Checklist
SKILL.md,README.md, andexamples/config.yamlare consistent./scripts/validate.shpasses locallyCHANGELOG.mdupdated (footer links only)🤖 Generated with Claude Code
https://claude.ai/code/session_01241uUFYvyppDmAq8ywxvGF
Generated by Claude Code