Problem
sep-40-oracle currently depends on soroban-sdk 25.x. In a workspace where other
contract crates have already migrated to soroban-sdk 26.1.0, including sep-40-oracle
as a dependency causes a resolver conflict and a build failure:
error[E0152]: duplicate lang item in crate soroban_sdk: panic_impl
= note: first definition in soroban_sdk loaded from .../libsoroban_sdk-.rlib
= note: second definition in soroban_sdk loaded from .../libsoroban_sdk-.rlib
This happens because Cargo ends up linking two distinct compiled copies of
soroban_sdk into the same wasm target — one pulled in transitively via
sep-40-oracle (soroban-sdk 25.x) and one via the rest of the workspace
(soroban-sdk 26.1.0). Since both copies define #[panic_handler], the build
fails with a duplicate lang item error before it even reaches normal type-checking.
Environment
- Target: wasm32v1-none
- soroban-sdk in the rest of the workspace: 26.1.0
- soroban-sdk pulled in via sep-40-oracle: 25.3.1 (confirmed via
cargo tree -i soroban-sdk)
Ask
Could a release be cut that bumps sep-40-oracle's soroban-sdk dependency to 26.x?
Per the soroban-sdk changelog, the 25→26 jump appears to be a relatively light
breaking-change surface (mainly the removal of the deprecated soroban-token-sdk
event format and a couple of internal macro/rename changes), so hopefully this
isn't a large lift on your end.
Happy to test against a pre-release branch if that's useful.
Problem
sep-40-oraclecurrently depends onsoroban-sdk25.x. In a workspace where othercontract crates have already migrated to
soroban-sdk26.1.0, includingsep-40-oracleas a dependency causes a resolver conflict and a build failure:
error[E0152]: duplicate lang item in crate
soroban_sdk:panic_impl= note: first definition in
soroban_sdkloaded from .../libsoroban_sdk-.rlib= note: second definition in
soroban_sdkloaded from .../libsoroban_sdk-.rlibThis happens because Cargo ends up linking two distinct compiled copies of
soroban_sdkinto the same wasm target — one pulled in transitively viasep-40-oracle(soroban-sdk 25.x) and one via the rest of the workspace(soroban-sdk 26.1.0). Since both copies define
#[panic_handler], the buildfails with a duplicate lang item error before it even reaches normal type-checking.
Environment
cargo tree -i soroban-sdk)Ask
Could a release be cut that bumps sep-40-oracle's soroban-sdk dependency to 26.x?
Per the soroban-sdk changelog, the 25→26 jump appears to be a relatively light
breaking-change surface (mainly the removal of the deprecated soroban-token-sdk
event format and a couple of internal macro/rename changes), so hopefully this
isn't a large lift on your end.
Happy to test against a pre-release branch if that's useful.