Document externally managed contract executables - #2775
Draft
leighmcculloch wants to merge 2 commits into
Draft
Conversation
|
Preview is available here: |
|
Preview is available here: |
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
1 participant
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
Add a guide to externally managed contract executables and mark every existing page that teaches
deploy_v2orupdate_current_contract_wasmwith the soroban-sdk v28 replacements,deploy_contractandupdate_current_contract.Why
stellar/rs-soroban-sdk#2020 landed CAP-85 support in soroban-sdk v28, deprecating both deployer entry points in favour of ones that take a
ContractExecutable, and the docs had no coverage of executable reference entries beyond a forward-looking mention in the storage strategies guide.