Skip to content

Move the smart-contracts skill to Protocol 29 and soroban-sdk 29 - #169

Merged
stellar-triage-bot[bot] merged 1 commit into
mainfrom
issue-agent/162-protocol-29
Nov 2, 2026
Merged

stellar-triage-bot[bot] merged 1 commit into
mainfrom
issue-agent/162-protocol-29

Conversation

@stellar-triage-bot

Copy link
Copy Markdown
Contributor

🤖 Automated message from the Stellar Triage Bot.

Closes #162. Mainnet and Testnet run Protocol 29, so the smart-contracts skill now targets soroban-sdk 29.

  • Bump the version text and both Cargo.toml pins to 29. The pin comment no longer says which protocol Mainnet runs.
  • The upgrade example uses update_current_contract(ContractExecutable::Wasm(..)). update_current_contract_wasm is deprecated since soroban-sdk 28.
  • The factory example uses deploy_contract, for the same reason (deploy_v2 is deprecated).
  • soroban-sdk 28+ rejects a plain cargo build for Wasm. The CI snippet and the eval build checks now use stellar contract build.
  • New eval scenario: smart-contracts/05-upgrade-entrypoint.json.

Verified: the new upgrade and factory code builds on soroban-sdk 29.0.1 for wasm32v1-none with no warnings. A plain cargo build fails with "soroban-sdk requires stellar-cli v25.2.0+".

Bump the version text and Cargo.toml pins from 27 to 29, and drop the
"which mainnet runs" clause so the comment does not go stale again.

soroban-sdk 28 deprecated update_current_contract_wasm and deploy_v2
(CAP-85), so the upgrade and factory examples now pass a
ContractExecutable to update_current_contract and deploy_contract.

soroban-sdk 28 also rejects a plain cargo build for a Wasm target, so
the CI snippet and the eval compile checks now use stellar contract
build. Add an upgrade eval scenario.
@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown
PR Preview Action v1.8.1

QR code for preview link

🚀 View preview at
https://stellar.github.io/stellar-dev-skill/pr/pr-169/

Built to branch gh-pages at 2026-11-02 22:27 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

@stellar-triage-bot

Copy link
Copy Markdown
Contributor Author

🤖 Automated message from the Stellar Triage Bot.

Verification at c2feedc:

  • Horizon reports Protocol 29 on Mainnet and Testnet. crates.io lists soroban-sdk 29.0.1 as the latest stable release.
  • The deprecations of update_current_contract_wasm and deploy_v2 come from the soroban-sdk v28.0.0 release notes and deploy.rs at v29.0.1.
  • The upgrade and factory code builds for wasm32v1-none on 29.0.1 with no warnings.
  • A plain cargo build fails as the new text says. The stellar/stellar-cli@v28.1.0 action and its Linux asset exist.
  • The preview check (full site build) passed. Copilot did not attach a review.

Merging.

@stellar-triage-bot
stellar-triage-bot Bot merged commit c50f7d8 into main Nov 2, 2026
7 checks passed
@stellar-triage-bot
stellar-triage-bot Bot deleted the issue-agent/162-protocol-29 branch November 2, 2026 22:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Smart Contracts skill pins soroban-sdk 27 and uses the deprecated update_current_contract_wasm; Mainnet runs Protocol 29

0 participants