Repository navigation
Prepare Maple Research 3.4.3 release - #1074
Merged
Merged
Conversation
Contributor
|
Maple development preview: https://70a7022b.maple-ca8.pages.dev Commit: Uses development API, billing, flags and PCR configuration. Cloudflare Access applies. |
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
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.
Prepare Maple Research 3.4.3 on current master
cd4218f5, advancing the pending 3.4.2 train because the US iOS App Store already publishes 3.4.2. Latest GitHub stable remains v3.4.1. This is a six-file version bump produced bynix develop --no-update-lock-file .#ci -c just update-version 3.4.3: Research manifests/Cargo.lock, Apple project/plist, and Android versionCode 2000028025 → 2000028026. No Agent, Auth, SDK, proxy, billing implementation, tag, or publication changes.Release highlights since v3.4.1: quota upgrade prompts and draft recovery (#1064), SDK attestation clock handling (#937), chat/composer/sidebar polish, iOS purchase/recovery and account-deletion presentation, and signing/build tooling. These describe existing master changes, not new implementation in this PR. #1073 remains under separate review; no candidate PRs were merged, and #1024 inclusion remains undecided.
Validation:
v3.4.3, Apple version parity, Android monotonicity andgit diff --check: passed.nix flake check --no-update-lock-file: passed on aarch64-darwin; incompatible systems omitted by Nix.prepare_macos_onnxruntimeprovisioned it; subsequent pinnedcargo check --lockedpassed. Lock delta is only the app version.5245921c1432c3d4c45cfcb16eaeef353c6a9b545352f1113490993061584ed9. Fixed Dev APIhttps://enclave.secretgpt.ai, Dev PCR policy, clientba5a14b5-d915-47b1-b7b1-afda52bc5fc6, Dev flags/billing endpoints. No login/runtime smoke claimed.cargo test --locked --all-targets(419 library + 3 CLI passed, 2 ignored).c211332cfacddaa7b0c186988646e32952867884. Fresh CI passed frontend/Rust tests, web, preview, release gates and supply-chain checks. Actual macOS/Linux/Windows desktop, Android fake-signed release, and iOS simulator builds passed. Windows desktop and downstream Windows artifact reproducibility verification passed; every exact-head workflow completed successfully.Release gates and concerns:
release from master, not codex/research-3.4.3. Merge will trigger normal production-shaped builds and TestFlight uploads. The PR remains draft and unmerged; complete the separate merge approval before that action.8d65dc6a91b7db5e92b1ac273b9248f8a3f440edb29b56d455574f62857f572d9ec9bc9773d031e8e1be2fc33d1fe847and Prod PCR016d3960ca1a7d1fb0700faf88ecdc5fcdeea3f9b7e1a0b1a1fa26b1fff0885a9548a3f40c5b18297067aacb20c26fdd9are absent from Research app fallbacks and shipped TypeScript/Rust SDK 4.0.1. Auth app fallbacks also lack them. Canonical signed-history endpoints are reachable, but fallback compatibility without fetching remains a release concern. The release skill/SDK rollout policy places refresh in a separate trust-rotation/consumer review before the isolated bump; no trust-policy edits here. Auth has an independent pin/publisher.No master push, tag, release, store upload, deployment, or other candidate PR merge performed.