chore: release vc-vault v0.4.0, vc-vault-factory v0.1.0, did-stellar-registry v0.2.0 (testnet)

[aguilar1x]

Summary

Release cut since vc-vault-v0.3.0, covering the post-v0.3.0 architecture change and the did-registry fixes already merged to dev.

Contract	Version	Change
vc-vault	0.3.0 → 0.4.0	single-tenant rearchitecture + open issuance (deny-by-exception) + fees moved to the factory; upgrade entrypoint removed (immutable code)
vc-vault-factory	— → 0.1.0	first release: deploys vaults (deterministic address from keccak(salt‖XDR(owner))), fee config, is_vault registry
did-stellar-registry	0.1.0 → 0.2.0	allow key reuse across verification relationships, reject duplicate service id_suffix, admin-role spec, clippy

Tooling / docs

• scripts/build.sh: builds the factory WASM.
• scripts/deploy.sh: factory deploy + the new vc-vault template install model (vaults are instantiated by the factory, not deployed standalone).
• docs/deployments/testnet.md and root README updated.

Testnet deploy (2026-06-22)

• did-stellar-registry v0.2.0: CBUNQ3GX3ZQ4MF64H7JCYZMXLGOS47VPIQQS7NCR6V3KX6YP7O72L5QF
• vc-vault-factory v0.1.0: CDRFQRIP4FA3WMPWCSAM3XEY6EM6EGKRYZRSCSVZ5NHCF6AGEVR2XEPQ
• vc-vault v0.4.0 template WASM hash: 2bd0323a98acb8469606808368da6c79824f2dd8391494b94ddbeb3d22c1a957

146 tests pass (58 + 61 + 27); factory verified on-chain (get_admin, is_vault).

[almanax-ai]

Plan expired

Your subscription has expired. Please renew your subscription to continue using CI/CD integration and other features.

[coderabbitai]

Warning

Review limit reached

@aguilar1x, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 32 minutes and 19 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a9691536-c267-4fd0-aa77-a6071868aeea

📥 Commits

Reviewing files that changed from the base of the PR and between c7bc73f and b709b4a.

📒 Files selected for processing (6)

• README.md
• contracts/vc-vault/README.md
• contracts/vc-vault/src/contract.rs
• contracts/vc-vault/src/events.rs
• contracts/vc-vault/src/interface.rs
• docs/deployments/testnet.md

📝 Walkthrough

Walkthrough

Bumps vc-vault to v0.4.0 and did-stellar-registry to v0.2.0. Adds vc-vault-factory as a new build and deploy target in the shell scripts, changes vc-vault deployment to a WASM-upload/template model, and records all new Testnet deployments in the documentation.

Changes

vc-vault-factory introduction and version bumps

Layer / File(s)	Summary
Crate version bumps and README badge contracts/vc-vault/Cargo.toml, contracts/did-stellar-registry/Cargo.toml, README.md	vc-vault-contract bumped to 0.4.0, did-stellar-registry bumped to 0.2.0, and the README release badge updated to v0.4.0.
build.sh: vc-vault-factory build target scripts/build.sh	Adds build_factory() to compile and optimize vc-vault-factory-contract WASM; extends the case dispatch and the all flow to include vc-vault-factory; updates usage message.
deploy.sh: factory deployment model scripts/deploy.sh	Rewrites deploy.sh for three targets: did-stellar-registry deploys with --admin, vc-vault uploads a template WASM and returns the hash, vc-vault-factory deploys with --vault_init_meta JSON. Adds require_wasm() helper, standardized WASM path variables, updated arg validation, and simplified end-of-script guidance.
Testnet deployment docs docs/deployments/testnet.md	Adds did-stellar-registry v0.2.0 row, new vc-vault-factory section with v0.1.0 entry, a description of the single-tenant vault architecture, and a vc-vault v0.4.0 template-deployed entry.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• ACTA-Team/contracts-acta#34: Also bumps the vc-vault crate version and adds new entries to docs/deployments/testnet.md, making it directly related to this release/versioning work.

Poem

🐇 A factory hops into the scene,
Uploading vaults to keep things clean.
The hash is passed, the template set,
No standalone deploy — no regret!
Version bumped and docs all neat,
This rabbit's build is quite complete. ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 66.67% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: releasing three contracts (vc-vault v0.4.0, vc-vault-factory v0.1.0, did-stellar-registry v0.2.0) on testnet.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/release-v0.4.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}