Repository navigation
Release v0.5.12 with file activity and managed updates - #235
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.
Codex and Claude now emit explicit native read, edit and search paths through Canonical/publication v5. Session Analytics groups those recorded facts by exact path and operation and links each selection to its final original tool update. Available history replays with stable source Event IDs and higher revisions; missing or redacted facts remain unavailable.
Release 0.5.12 uses the target-owned managed channel and catalog v3. The genuine published 0.5.11 bridge retains npm/GitHub Latest and legacy discovery routes for returning old clients. Formal release acceptance acquires its eight immutable public archives once, revalidates their fixed identity for every case, and exercises normal .10→.11→.12 delivery plus four installed interruption/recovery cases. The historical .9 stopped clock transition reaches the real .11 bridge, then explicitly enables and dispatches its actual automatic worker to .12 in the same installation. Stop intent remains authoritative. The test explicitly disables automatic updates after the second leg.
The .12 CLIUpgrade and ToolUpdates Modules preserve the global npm entry for v3 manual updates and stop offering a false same-version entry refresh. Complete-bundle preparation, activation, ownership, migration and Adapter alignment still run; v1/v2 compatibility replacement remains intact. The immutable published .11 manual menu limitation is disclosed in release notes and retained failed acceptance logs.
Validation: local repository checks, production build, complete PostgreSQL/provider integration, race/fuzz, dependency security, release policy, self-host configuration/paired restore and candidate image builds passed. Full installed release acceptance passed against the final checksummed packages: genuine .10→.11→.12 automatic delivery and all four interruption/recovery cases, with actual nonempty journal receipts. The historical .9 stopped bridge transition also passed. The observed genuine journal format is 8→8; a separate untouched installed candidate contract verifies controlled SQL7→8. Manual application caller tests passed 39/39. Candidate evidence retains the earlier failed attempts and their corrections. Exact-head CI and Security remain required PR checks.
SQL remains at 24. Deploy the v5-capable Server before advertising .12; accepting v5 creates a durable format boundary, so a pre-v5 image alone cannot restore compatibility. The explicit publication request authorizes the documented manual-only staging waiver. Native Windows lifecycle, live Claude/Cursor, real OAuth/login/wake and the ten listed manual staging checks remain unverified.