Repository navigation
chore: prepare next Research, SDK, and proxy patches - #1291
Merged
Merged
Conversation
Contributor
|
Maple development preview: https://b40a95ce.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 the next development versions after Research v3.4.5:
Research's Android version code advances to 2000028029, with matching Apple version metadata. Update the four Cargo lockfiles' local package records to keep consumers consistent. Maple Work's own version and release configuration remain unchanged; its lockfile only follows the shared SDK/proxy versions.
Validation completed:
cargo checkthrough the pinned ONNX wrapper; all 13 aarch64-darwin flake checks.cargo test --locked --all-targets: 430 passed, 2 ignored by the existing suite.The default local Research Rust run segfaulted in macOS
libunwindwhile the panic hook printed a backtrace for the intentional parser-panic containment test. The same focused test reproduced the crash with backtraces enabled and passed withRUST_BACKTRACE=0. The complete Research Rust gate then passed with only backtrace printing disabled after entering the pinned Nix shell; all tests and assertions remained enabled. No test, hook, toolchain, or application source was changed for this workaround. The remaining SDK, proxy, and Work component hooks then passed in their owning pinned shells, using the supportedMAPLE_HOOK_ONLYselector for those remaining components.Need help on this PR? Tag
@codesmith-botwith what you need.