Repository navigation
chore(release): prepare v0.2.0 - #23
Merged
Merged
Conversation
Bump the korg runtime crates from 0.1.0 to 0.2.0 (korg-bridge keeps its own bridge-v* line) and cut the [0.2.0] changelog section from Unreleased, filling in the merged work it was missing (#8-#22). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QsuMoxNk88vZYnxPepuUKV
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.
Requested by dusk · project thread
Before: the runtime crates still say 0.1.0, and everything merged since May sits under
[Unreleased]in the changelog, which also leaves out the swarm honest pipeline, capture, trust hardening, the goldseal rename and the README launch work (#8 to #22).After: the korg runtime crates are 0.2.0, and the changelog has a
[0.2.0] — 2026-10-05section with a summary, a breaking-change note forgoldseal@v1→korgcert@v1, and entries for the missing PRs.[Unreleased]is empty again.How: bumped
versionin the root and the tencrates/korg-*manifests plus the two internalkorg-ledgerdependency pins, then let cargo refreshCargo.lock(only korg's own packages changed).korg-bridgestays on its ownbridge-v*line.cargo check --workspace --lockedpasses.No tag is pushed by this PR. After merge, pushing
v0.2.0triggersrelease.yml, which builds the four binaries and publishes the GitHub release.🤖 Generated with Claude Code
https://claude.ai/code/session_01QsuMoxNk88vZYnxPepuUKV
Generated by Claude Code