Repository navigation
fix: preserve compressed Codex history and release v1.6.1 - #57
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 now compresses archived session logs as
.jsonl.zst. The collector only discovered.jsonl, so compressed sessions disappeared from SQLite and were propagated as deletions to the Mesh hub. Read Zstandard archives directly and retain the existing session identities, calls and tokens, including when compressed and plain copies coexist.An archive read failure now rejects the partial refresh, preserving the last successful snapshot and skipping downstream synchronization. Prepare version 1.6.1, document the Node 22.15 minimum and upgrade path, and add a container regression to CI.
Validation: 342 root tests pass. Docker HTTP smoke checks plain-to-compressed history and corrupt-archive retention in a non-root read-only container. The existing storage smoke verifies migration, persistent data/identity and container replacement. The live affected machine's history was rebuilt from its original compressed archives and verified in the private hub and browser, including June through October.