chore(release): bump to 0.7.0; record v0.6 + v0.7 milestones in CHANGELOG#45
Merged
Conversation
…ELOG Both 1.0 launch-gate milestones are merged in code but the version was stuck at 0.5.1 with no changelog entries for either: - v0.6 money & concurrency correctness (#26–#30, #38) — merged via #41/#44. - v0.7 security hardening (#31–#37) — merged via #42. Bump version (pyproject + __init__) to 0.7.0 and add [0.6.0] and [0.7.0] CHANGELOG sections so the version reflects reality. No behavior change; no launch switches flipped — the roadmap's v0.7 exit (external security review) remains a separate human gate before public launch. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
tcconnally
force-pushed
the
v0.7-security
branch
from
5d581ef to
23aef13
Compare
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.
Why
Both 1.0 launch-gate milestones are already merged in code, but the repo was still labelled
0.5.1with no changelog entries for either — a version-honesty gap (foundation-first).(The handoff listed v0.7 as "untouched" — that was stale; the code is in
mainand verified present.)What
pyproject.toml+plutus_agent/__init__.py)0.5.1→ 0.7.0.[0.6.0]and[0.7.0]CHANGELOG sections documenting the merged work.Docs/metadata only — no code or behavior change. Full suite green (118 passed).
Not in scope / explicitly not done
No launch switches flipped. The roadmap's v0.7 exit criterion — an external security-review pass on the public surface, and turning on
PLUTUS_ALLOW_SIGNUP— remains a separate human gate before any public launch.🤖 Generated with Claude Code