docs: update stale miden-vm version in dependency diagram

[amathxbt]

The dependency diagram references miden-vm v0.19.1 but the release manifest example and latest release is v0.20.0. Updated for consistency.

[Keinberger]

Hey @amathxbt, thanks for catching the stale versions in the diagram!

The version labels in the diagram refer to what cut-versions.yml used for the last versioned snapshot. Those values come from .release/release-manifest.yml, which currently has different versions than what your PR proposes (e.g. miden-vm is at v0.20.6 in the manifest, not v0.20.0). The other three repos (miden-base, miden-node, miden-client) are also outdated in the diagram.

I think the better fix here is to replace the specific version tags in the diagram with something generic like @<release-tag>, so the README doesn't go stale every time we cut a new version. We can add a note pointing to .release/release-manifest.yml as the source of truth for the actual pinned refs.

Would you be up for making that change? Let me know if you have questions about how the versioning works!

Thanks!

[amathxbt]

Thanks for the clarification! I've updated the diagram to use "" instead of fixed versions for the CutVersions workflow.

[BrianSeong99]

Thanks for flagging the stale versions. Replacing them with placeholders loses useful information though, and the diff has indentation issues that would break the Mermaid rendering. Closing this — we'll address the stale versions separately.

[BrianSeong99]

I was closing different PRs claude coded the wrong PR, apologies, I'll review this and merge this today after testing it locally

[BrianSeong99]

Yeah, I agree, still sharpening my claude skill😂On Mar 22, 2026, at 14:45, AMATH ***@***.***> wrote:amathxbt left a comment (0xMiden/docs#190) Ok good 👍 coz seems is totally different reaction there's zero idea to close it IMO —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: ***@***.***>