Prepare for v0.2.0: close out the changelog - #10
Merged
Conversation
Everything under [Unreleased] shipped with the delegation work: plans, `ike delegate`, the separate agent gate, interactive sessions, and the per-run effort level. Done by hand and before tagging, because the GitHub release notes are generated from commit subjects (`changelog: use: github`) rather than from this file — so a tag pushed first leaves CHANGELOG.md describing a version that has already gone out as "unreleased". 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.
Turns
## [Unreleased]into## [0.2.0] - 2026-08-01and adds the comparelinks, ahead of tagging
v0.2.0.Everything in the section shipped with #9: plans,
ike delegate, the separateagent gate, interactive sessions pinned to a task, and the per-run effort level.
A minor bump rather than a patch — it is all new surface, and nothing in it
breaks an existing data file (
dirandplan_atwere added within v4 asomitempty).Done by hand, and before the tag, because the release workflow generates GitHub
release notes from commit subjects (
changelog: use: github) rather than fromthis file. Tagging first would leave CHANGELOG.md describing a version that had
already gone out as "unreleased".
No code changes.
🤖 Generated with Claude Code