Repository navigation
chore: release v0.7.0 - #9
Merged
Merged
Conversation
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.
Cuts the tool report (#8) as v0.7.0: dates the
[Unreleased]block, refreshes the compare links, and bumps both manifests.The version lives in
.claude-plugin/plugin.jsonand.codex-plugin/plugin.json— the two marketplace files carry none — and it is what lich's update gate compares against, so this is the commit that makes Settings › Updates offer the tool line to anyone running it.Pairs with lich's own release: the feature needs a lich that understands
tool/detail(unreleased at the time of writing,mainonly). An older lich ignores both fields, so shipping the plugin first is safe — the card just stays as it was until lich catches up.Test plan
node --test tests/*.test.mjs— 85 pass[Unreleased]/[0.7.0]compare links point at v0.7.0