v2.1.0

registry-publish-assets can now publish releases from repos with their own pipeline: a version input for assets named .wasm, a packages input to choose which assets publish, and upload + publish-hash for Wasms over publish_max_wasm_bytes (#24). A run with no publishable asset now fails instead of passing. registry-publish now deploys even when the publish was already done (#23).

v2.0.0

Breaking: contract-release now defaults to rustc 1.99.1, stellar-scaffold-cli 0.0.31 and stellar-cli 28.1.0 (#22). These versions are embedded in the built Wasm, so callers relying on the defaults get new release hashes. To keep v1 builds, pass rust_toolchain: 1.99.0, scaffold_version: 0.0.27 and stellar_cli_version: 26.0.0.

v1.0.0

First tagged release of the reusable workflows (detect-releases, release-pr, contract-release, registry-publish, registry-publish-assets) at 839f1e9.

Recent changes included:

• release-pr refreshes Cargo.lock after version bumps (#20)
• contract-release pins rustc, stellar-cli and scaffold, with defaults matching perch's 2026-10 tier-0 releases (#18)
• registry-publish takes an optional environment input (#18) and publishes in one transaction when the Wasm fits (#15)