Repository navigation
chore(release): prepare 0.7.0 contract fixes - #20
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
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
Prepare version 0.7.0 for the contract fixes merged in #19. Align package metadata and move the completed changelog into 0.7.0, retaining budget and usage migration notes. Leave Unreleased empty for the next batch.
Why
The Managed budget request field changed from a monetary object to decimal-string
max_credit_cost, requiring a minor release while pre-1.0. This batch also carries Session/SSE Credits, Identity ownership query parameters, and existing channel pairing corrections. Remaining existing-API contract updates are planned for 0.8.0; missing API endpoints are excluded.Verification
make check-version VERSION=0.7.0,go test ./convention.git diff --check.run_live=true,run_sa=true, andsa_execution=true; CN/Global checks and artifact digests verified.The merged feature PR has offline and targeted CN PAT live evidence. The candidate package also passed internal CN/Global integration and SA authentication/execution checks. Real channel pairing and compaction were not covered. The stable suites retain documented exclusions; automated checks do not constitute a human QA sign-off.
Impact
This PR changes release metadata only; public types, generated API docs, fixtures, and examples are unchanged. GitHub publication follows internal verification and the existing human Environment approval.
An initial CN Skill/Memory model-response assertion failed. An unchanged focused reproduction and one internal pipeline rerun passed; the initial failure record is retained. No assertion was weakened or skipped.