chore: release v0.6.0 - #10
Merged
Merged
Conversation
Roll the Unreleased changes (go-didcomm v0.5.0 bump, sender-authenticating Receive / new ReceiveUnverified, TAPResult SenderDID) into a 0.6.0 heading. v0.5.0 was already tagged on an earlier commit, so this release is v0.6.0.
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 release for the merged go-didcomm v0.5.0 bump.
UnreleasedCHANGELOG entries under a## [0.6.0] - 2026-07-08heading. No code changes.v0.5.0git tag already exists on an earlier commit (PR feat(taip-9)!: ConfirmRelationship body matches the spec Agent payload #7), so the next free tag isv0.6.0. Pre-1.0, the breakingReceive/TAPResultchange is a minor bump.After merge
Tag
mainto publish (Go modules release by tag — no registry step):