chore: bump submodules to Miden v0.15 + align parent docs - #20
Merged
Conversation
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.
What & why
Points the two template submodules at their Miden v0.15 commits and aligns the parent-level docs with the v0.15 source-repo renames. The parent repo has no direct Miden SDK dependency — it "gets v15" by moving its gitlink pointers and keeping
CLAUDE.md/README.mdconsistent.Submodule bumps
project-template5270c0a80394cdchore/sync-skills-v15project-templatemain).frontend-template8a9fcf0c5c3ad1kbg/chore/v15-migrationchore(skills): sync frontend skills to v0.15commit one commit on top of #21, currently the branch head, not yet inmainand with no open PR of its own.project-template80394cd—chore(skills): sync skills to miden v0.15(2026-07-01)frontend-templatec5c3ad1—chore(skills): sync frontend skills to v0.15 from 0xMiden/agent-tools#12(2026-07-01)Both pinned commits are unmerged by design — this PR pins the v0.15 template commits intentionally. Note the asymmetry above: project-template's pin is on an open PR (#52), while frontend-template's v0.15 work already merged (#21) and the pin is a small follow-up skills-sync commit that has no open PR of its own. If either branch is force-pushed/rebased or the frontend commit is superseded, re-pin to the new head and re-bump.
Parent-doc alignment
Derived from the actual v0.15 submodule skill diffs. The v0.15 source-guide skills renamed the repositories they map, so the parent docs were updated to match:
miden-base→protocol(0xMiden/protocol, cratemiden-protocol)miden-client→rust-sdk(Rust client) forrust-sdk-source-guide; →web-sdkforfrontend-source-guidecompiler,tutorialsunchangedEdits (4 lines,
CLAUDE.md×3 +README.md×1):CLAUDE.md—rust-sdk-source-guiderow →protocol,compiler,rust-sdk,tutorialsCLAUDE.md—frontend-source-guiderow →web-sdkCLAUDE.md— Factuality rule repo list →protocol,compiler,rust-sdk,web-sdk,tutorialsREADME.md— "go deeper" verify-in-source list →protocol,rust-sdk,web-sdk,compiler,tutorialsEverything else was "no change" and verified so:
agent-toolsstill has exactly 22 skills (no new "protocol" skill), so the parent's "22 upstream / 9 upstream-only / 13 mirrored" counts are accurate — unchanged.agent-toolscontributor skills (rust-client-patterns,idxdb-patterns,wasm-bridge) are not v0.15-migrated and still referencemiden-client; the parent descriptions of them are left asmiden-clienton purpose so they keep matching the real upstream skills.miden-client-cliskill still invokes the CLI asmiden client(via midenup) — unchanged.cargo miden build,cargo test -p integration,validate_local,miden-node bundled start,yarn dev,npx vitest --runall still valid).0.14version strings existed in parent-level files (and none introduced).Verification log
git submodule status→+80394cd project-template,+c5c3ad1 frontend-template(pinned SHAs).git fetch+git cat-file -t <sha>→commit) and are the current head of their named branch; both are unmerged (not in their submodulemain).git grep "0\.14"over parent-tracked files (excluding submodules) → 0 matches.git grep "miden-base"over parent-tracked files → 0 matches (all migrated toprotocol).verify-all.sh:cargo test -p integration --release,cargo-miden 0.9.0): PASS — v0.15 contracts (counter-account,increment-note) compile and thecounter_testMockChain integration test passes (test result: ok. 1 passed; 0 failed, exit 0; only a benignwide-arithmeticcompiler warning).@miden-sdk/* 0.15.3but the localnode_modulesis from the prior v0.14 checkout. Making it pass needs a fresh v0.15yarn install, which is frontend-template setup owned by its own PR/CI and would mutate the submodule working tree (out of scope for a pointer bump). The frontend v0.15 build/test is covered by frontend-template#21's own CI.Scope
.gitmodulesleft unchanged (pins are commits, not branches).