Repository navigation
Prepare qntm v0.6.2 release - #27
Merged
Merged
Conversation
This branch was successfully deployed
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.
The fixes accumulated on main since v0.6.1 are ready for a coordinated package and deployment release. This prepares v0.6.2 with aligned Python, TypeScript, browser, terminal and Claude plugin versions, curated release notes, and documentation that identifies the newly available client features.
The release includes reviewed terminal and native OpenClaw gateway actions, Python charter APIs, encrypted browser backups and restore validation, stricter signature and expiry handling, invite-link privacy fixes, and documented monitoring and backup behavior. Contact-based group welcomes remain in draft PR #26 and are excluded from this point release.
Validation: full candidate CI passed at d8a4ced. Release metadata and generated CLI help match, the uv lock is consistent, all five release-script tests pass, and whitespace checks pass. Fresh wheel/npm installs completed authenticated messaging through the live relay and pinned charter audits. An encrypted charter backup was restored in isolation and verified with both clients against the original registrar identity and retained checkpoint. The release tag runs its publication gate before any package or service deployment.