Repository navigation
release: RC.3 migration, Connections and scheduled results - #31
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.
RC.2 downloads do not contain the migration, Connections and scheduled-result changes already on main. This candidate bundles them as 0.20.0-rc.3 and aligns the installer, website, README and changelog.
Migration stays fingerprint-confirmed and inactive by default; connector drafts carry no credentials or authority. Scheduled results have a separate labelled notification. RC.3 starts a new observation window before stable.
Qualified signed commit: 75a8274. Native Linux/macOS Python3.11 CI passed; local Python3.12, Python3.13 and ARM64 each passed 3599 tests with 3 explicit skips. Adversarial suite277/277; real Opus5.5 E2E44/44. Both macOS and ARM64 signed clean install, RC.2→RC.3 state/schedule migration and rollback passed. OSV0 across four locks and installed environments; public hygiene clean, historical secret-scan findings match the reviewed synthetic baseline. The existing Ed25519 signing pin verified the exact archive and rejected tampering.