Repository navigation
proxy: 0.4.2, the first version serving POST /v1/systemone - #1088
Merged
Merged
Conversation
The next Maple release publishes proxy archives and a GHCR image only for a new proxy version, and 0.4.1 already shipped with v3.4.3. Bump to 0.4.2 so the System One route reaches the standalone proxy's release channels. The embedding desktops' lockfiles follow (their ^0.4.0 requirement is unchanged; the lockfiles were regenerated with each workspace's own pinned cargo), and the README version notes move along. Co-Authored-By: Claude Fable 5.1 <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
1 participant
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.
Why
The System One endpoint (#1045) is served by the standalone proxy and by both desktops' embedded proxies as built from this repository, but the proxy's release channels only move on a new proxy version: the Maple release workflow attaches native
maple-proxyarchives per release, and the GHCR sibling builds an image only for a new, non-baseline version.0.4.1already shipped with v3.4.3 (archives andghcr.io/mapleprivacylabs/maple-proxy:0.4.1), so the next release would carry the new route under the old version string and no new image tag.Changes
proxy/Cargo.toml0.4.1 → 0.4.2 (proxy/Cargo.lockfollows).apps/maple-agent/Cargo.lockand the Research native shell'sCargo.lockpick up the path dependency's new version; their^0.4.0requirement is unchanged. Regenerated with each workspace's own pinned cargo (the remaining hunks are that cargo's rendering of already-lockedwindows-sysedges; no other package version changes).proxy/README.mdversion notes ("prepares proxy 0.4.2", "next prepared proxy version").Verification
cargo metadata --lockedpasses for the proxy and both desktop workspaces.Publication itself happens through the next Maple release (archives + GHCR image); nothing here publishes. The SDK publications (
maple-sdk4.1.0,@mapleai/sdk4.2.0) are separate workflow runs.🤖 Generated with Claude Code