Repository navigation
fix(deps): update stellar-registry to 0.1.2 - #288
Merged
zachfedor merged 1 commit intoNov 2, 2026
Merged
Conversation
Asset imports in 0.1.1 baked in the XLM contract address for whichever network the contract was compiled for, so a cached testnet build made guess-the-number's `reset` fail on local. 0.1.2 resolves the address at runtime instead.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
zachfedor
approved these changes
Nov 2, 2026
Contributor
|
Thanks @ElliotFriend! |
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.
What
Updates
stellar-registryandstellar-registry-macrofrom 0.1.1 to 0.1.2 (Cargo.lockonly).In 0.1.1,
import_asset!("xlm")bakes in the XLM contract address for the network the contract is compiled for, and Cargo doesn't rebuild when that network changes. After a testnet build, the cached Wasm is reused for local, soresetfails:0.1.2 resolves the address at runtime, so one Wasm works on every network (stellar-registry/cli#97). The macro's generated API is unchanged, so no contract code changes.
Testing
cargo test -p guess-the-numberpassesRefs stellar-registry/cli#97