Repository navigation
chore(release): PseudoCode 0.0.68 - #48
Merged
Merged
Conversation
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
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.
Problem
The merged mailbox improvements need a new desktop version so installed clients can detect and download the update without replacing 0.0.67 artifacts.
Change
Bump the four release package manifests together to 0.0.68 using the established release script. This release includes the mailbox status, mobile parity, and conversation audit changes merged in #47. The native iOS release uses its next App Store Connect build number independently.
Scope and approval
The fork maintainer explicitly authorized committing, merging after green CI, and building the ARM64 Mac and iOS releases.
Verification
The version update changes only the four manifest version fields, and staged formatting passed. #47 passed full CI before merging; this version commit must pass its own CI before release builds start. The ship-pseudocode workflow will verify signing/notarization and the native archive build number before publishing/uploading.
Model: GPT-6.1-Sol. Harness: Codex in PseudoCode.