Repository navigation
fix(stellar-scaffold-cli): expose build --compile-only flag - #637
Merged
Merged
Conversation
Officially encouraged Stellar Scaffold deploy process: 1. Build Wasm binaries for testnet 2. Publish & deploy them with Stellar Registry CLI 3. Update `testnet` sections of `scaffold.yml` to point at deployed instances (using contract IDs or Registry names) By default, version 2 builds also deploy contracts and generate clients. That prevents compiling Wasm independently when testnet client generation depends on contracts that have not been deployed yet. Expose the existing --compile-only flag so users can build Wasm before publishing and deploying it through Stellar Registry CLI, without triggering Scaffold deployment or client generation. --compile-only still validates scaffold.yml, including settings for all declared networks. Contract IDs and Registry names must be syntactically valid, but their referenced contracts need not exist yet: this build skips the deployment/client-generation steps that would attempt to use them.
willemneal
approved these changes
Oct 21, 2026
Merged
chadoh
pushed a commit
that referenced
this pull request
Oct 21, 2026
## 🤖 New release
* `stellar-scaffold-ext-types`: 0.0.4 -> 0.0.5 (✓ API compatible
changes)
* `stellar-scaffold-cli`: 0.0.30 -> 0.0.31 (⚠ API breaking changes)
* `stellar-scaffold-reporter`: 0.1.3 -> 0.1.4
### ⚠ `stellar-scaffold-cli` breaking changes
```text
--- failure constructible_struct_adds_field: struct exhaustively constructible through public API adds field ---
Description:
A pub struct that could be exhaustively constructed with a literal using only public API has a new pub field, breaking existing exhaustive literals.
ref: https://doc.rust-lang.org/reference/expressions/struct-expr.html
impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.51.0/src/lints/constructible_struct_adds_field.ron
Failed in:
field Command.compile_only in /tmp/.tmp7uanvi/cli/crates/stellar-scaffold-cli/src/commands/build/mod.rs:38
--- failure enum_variant_added: enum variant added on exhaustive enum ---
Description:
A publicly-visible enum without #[non_exhaustive] has a new variant.
ref: https://doc.rust-lang.org/cargo/reference/semver.html#enum-variant-new
impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.51.0/src/lints/enum_variant_added.ron
Failed in:
variant Error:State in /tmp/.tmp7uanvi/cli/crates/stellar-scaffold-cli/src/commands/build/clients.rs:153
--- failure enum_variant_missing: pub enum variant removed or renamed ---
Description:
A publicly-visible enum has at least one variant that is no longer available under its prior name. It may have been renamed or removed entirely.
ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.51.0/src/lints/enum_variant_missing.ron
Failed in:
variant Error::NetworkConfig, previously in file /tmp/.tmpdxkV6L/stellar-scaffold-cli/src/commands/clean.rs:26
variant Error::EnvToml, previously in file /tmp/.tmpdxkV6L/stellar-scaffold-cli/src/commands/clean.rs:29
```
<details><summary><i><b>Changelog</b></i></summary><p>
## `stellar-scaffold-ext-types`
<blockquote>
##
[0.0.5](stellar-scaffold-ext-types-v0.0.4...stellar-scaffold-ext-types-v0.0.5)
- 2026-10-21
### Added
- config-driven builds with per-checkout deployment state
([#630](#630))
</blockquote>
## `stellar-scaffold-cli`
<blockquote>
##
[0.0.31](stellar-scaffold-cli-v0.0.30...stellar-scaffold-cli-v0.0.31)
- 2026-10-21
### Added
- config-driven builds with per-checkout deployment state
([#630](#630))
### Fixed
- *(stellar-scaffold-cli)* expose `build --compile-only` flag
([#637](#637))
</blockquote>
## `stellar-scaffold-reporter`
<blockquote>
##
[0.1.4](stellar-scaffold-reporter-v0.1.3...stellar-scaffold-reporter-v0.1.4)
- 2026-10-21
### Other
- updated the following local packages: stellar-scaffold-ext-types
</blockquote>
</p></details>
---
This PR was generated with
[release-plz](https://github.com/release-plz/release-plz/).
Co-authored-by: aha-release-plz[bot] <211513279+aha-release-plz[bot]@users.noreply.github.com>
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.
Note: needed because in #630 Zach and I made
--build-clientsthe defaultOfficially encouraged Stellar Scaffold deploy process:
testnetsections ofscaffold.ymlto point at deployedinstances (using contract IDs or Registry names)
By default, version 2 builds also deploy contracts and generate clients.
That prevents compiling Wasm independently when testnet client generation
depends on contracts that have not been deployed yet.
Expose the existing --compile-only flag so users can build Wasm before
publishing and deploying it through Stellar Registry CLI, without
triggering Scaffold deployment or client generation.
--compile-only still validates scaffold.yml, including settings for
all declared networks. Contract IDs and Registry names must be
syntactically valid, but their referenced contracts need not exist yet:
this build skips the deployment/client-generation steps that would
attempt to use them.