chore: migrate project template to Miden v0.16 - #61
Merged
Conversation
This was referenced Sep 4, 2026
greenhat
approved these changes
Sep 7, 2026
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.
Overview
This PR synchronizes the standalone project-template code with the Miden v0.16 template rendered from
0xMiden/compiler@nextat52abe7d76d5757dae3ca074b16a3cea361fa5a4e. The seven.claude/skillsfiles are intentionally excluded and are handled in stacked draft PR #64.Key Changes
miden = "0.14"guest SDK andmiden-sdk-build-script-support = "0.14"build.rsfiles that prepare the package cache for ordinary Cargo and IDE buildsCargo.lockfiles absent, matching the compiler template policy for these standalone library crates, while retaining the root workspace lockfile0.16.0toolchain through midenup in CICompiler Template Parity
The rendered compiler workflow invokes
midenc --versiondirectly and exportsMIDENUP_HOME. GitHub Actions proved two midenup 1.0 integration problems with those exact lines:midencis exposed through themidendispatcher, and exportingMIDENUP_HOMEmakes the unchanged helper selectmiden build, which now dispatches tomidencrather thancargo-midenand therefore fails to build the contract Cargo manifest.This PR keeps the upstream helper unchanged and applies only the workflow correction: verify with
miden midenc --version, add the active toolchainoptdirectory toGITHUB_PATH, and let the helper use its existingcargo midenfallback.Skills Follow-up
Issue #63 tracks the v0.16 skills migration. Draft PR #64 is stacked on this branch and sources the six shared skills from 0xMiden/agent-tools#17, with the project-only
miden-client-cliskill migrated separately.Tests
Both contracts build with
cargo-miden 0.10.0, and the integration suite passes with exactly onecounter_test, zero failures, and zero ignored tests. GitHub CI passed end to end in run33879688492, including the contract rebuilds performed by the integration test.