Repository navigation
Prepare maple-sdk 5.0.0 and maple-proxy 0.5.1 for crates.io - #1671
Merged
Merged
Conversation
The Rust SDK lost public Transport V1 items in #1650, so its next publication is a major version. The proxy moves to 0.5.1 because its runtime changed since the released 0.5.0 (#1627) and it now requires maple-sdk 5.0.0. Only the two local package entries change in each lockfile. Co-Authored-By: Claude <noreply@anthropic.com>
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.
Sets the versions for a crates.io release of the proxy, which has been stuck at 0.3.2 (August) and therefore still on Transport V1, which the hosted backend no longer serves.
maple-sdk4.2.0 → 5.0.0. 4.2.0 was never published, and SDK: remove unused Transport V1 code #1650 removed public Transport V1 items from the crate (the V1cryptohelpers, threeSessionManagermethods, five request/response types andError::KeyExchange), so the next publication has to be a major version. The Rust SDK README lists what was removed.maple-proxy0.5.0 → 0.5.1, requiringmaple-sdk5.0.0. The released 0.5.0 (Maple 3.4.9, containerlatest) predates thecontext_length_exceededhandling from fix(opensecret): return context_length_exceeded for provider context rejections #1627, so the proxy's runtime has changed and needs its own version. The next Maple release will publish the 0.5.1 container through the existing sibling workflow.sdk/rust,proxy,apps/maple-agent, Researchsrc-tauri). No registry dependency moves.cargo metadata --locked --offlinepasses for each in its pinned shell.Not in this PR: nothing is published by merging it. The npm package
@mapleai/sdkis untouched; #1650 removed TypeScript exports too, so its next version is its own decision. In-repo consumers keep building the in-tree SDK, so no application behavior changes.After merge: publish
maple-sdk5.0.0 withsdk-publish-rust.yml, then inspect the proxy package withcargo package --locked --manifest-path proxy/Cargo.tomland publishmaple-proxy0.5.1, which is still a manual step.🤖 Generated with Claude Code
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.