Repository navigation
Rename SDKs to @mapleai/sdk and maple-sdk - #895
Merged
Merged
Conversation
Contributor
|
Maple development preview: https://ae5b602f.maple-ca8.pages.dev Commit: Uses development API, billing, flags and PCR configuration. Cloudflare Access applies. |
AnthonyRonning
marked this pull request as ready for review
September 9, 2026 00:37
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.
The monorepo SDKs now use
@mapleai/sdkfor TypeScript/React andmaple-sdk(maple_sdkimports) for Rust. Research, Agent and the proxy consume the renamed in-tree packages, with matching package metadata, examples, build artifacts and dependency checks.This PR changes source package identities and in-tree consumers; it does not publish either SDK. Registry bootstrap and protected publishing workflows are a separate next step.
The existing SDK versions remain 3.5.2 (TypeScript) and 3.6.2 (Rust). Exported APIs such as
OpenSecretProviderandOpenSecretClient, backend identity, configuration variables, protocol headers, encrypted transport and signed-PCR verification remain unchanged.Fresh tarball consumers exposed two inherited packaging defects. The CommonJS entry now uses
.cjswith a matching.d.ctsdeclaration and conditional type exports. The existing pinned OpenAI dependency moves from development to package dependencies because publicModeldeclarations import its types. These corrections preserve the exported API.Local validation: TypeScript SDK 123 tests pass (3 credential-dependent skips); the seven-file package passes ESM, CommonJS, UMD, strict Bundler and strict NodeNext consumer checks. All 45 runtime exports and public declarations match the original package. Research's full frontend gate passes 818 tests. Rust SDK strict Clippy, 85 tests, rustdoc and extracted 34-file crate build pass. Proxy strict Clippy, 27 tests, rustdoc and Machete pass; Research native tests pass 415 tests (2 ignored). Both consumer dependency verifiers and all nine local root flake checks pass. Independent source/integration review found no actionable issue.
The complete normal commit hook passes, including all 818 frontend and 415 native Research tests (2 existing ignores), with two Rust test workers to reduce local VM contention. Canonical Research formatting and strict Clippy pass on its actual pinned 1.94.1 toolchain; the extra all-target Clippy run reports eight existing test-only diagnostics in unchanged code. SDK and proxy formatting/strict Clippy also pass with their actual pinned 1.89.0 tools.
Local Cargo subcommand lookup initially selected rustup's installed toolchain; corrected checks use process-local
RUSTUP_TOOLCHAINpointing to each Nix toolchain, without global configuration changes. Agent's warning-denied workspace build, 725 workspace tests and 30 headless tests pass (755 total, with 3 existing ignores); formatting and all four strict Clippy modes also pass on its actual pinned 1.98.0 toolchain. Proxy crates.io packaging requires the new SDK to be published; local path builds are the validation available in this source-only round.