feat(channel-auth): wrap asset enable/disable + refresh artifacts for core 0.3.0#36
Merged
Merged
Conversation
… core 0.3.0 soroban-core 0.3.0 adds quorum-gated `enable_channel` / `disable_channel` to the Channel Auth contract (+ `ChannelStateChanged` event and an expanded error enum). Track it the same way as #34: - channel-auth: add `enable_channel` / `disable_channel` to AuthInvokeMethods, EnableChannelInput / DisableChannelInput to types, and regenerate AuthSpec from the 0.3.0 contract (18 → 22 spec entries: new fns, ChannelStateChanged, expanded MoonlightError). - refresh compiled `channel_auth_contract.wasm` + `privacy_channel.wasm` artifacts from the 0.3.0 build (privacy-channel changed via the shared error enum). version: 0.9.1 -> 0.10.0
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Why
soroban-core 0.3.0 (PR #33) adds quorum-gated
enable_channel/disable_channelto the Channel Auth contract, plus aChannelStateChangedevent and an expanded error enum. The SDK bundles the contract artifacts + method map, so it has to track the new core version — same cascade as #34 ("update contract artifacts for latest core").Changes
enable_channel/disable_channeltoAuthInvokeMethods; addEnableChannelInput/DisableChannelInput(both{ channel, asset }) toAuthInvoke; regenerateAuthSpecfrom the 0.3.0 contract (18 → 22 entries — the two new fns,ChannelStateChanged, and the expandedMoonlightError).test/contracts/channel_auth_contract.wasm+privacy_channel.wasmfrom the 0.3.0 build (privacy-channel's hash changed via the shared error enum).version: 0.9.1 → 0.10.0.Verification
deno fmt --check(103 files) /deno lint/deno check mod.ts/deno task test:unit→ 16 passed, 0 failed.stellar contract bindingsagainst the freshly-built 0.3.0 WASM (which exportsenable_channel/disable_channel).Merge ordering
Merge after soroban-core #33 releases, so the bundled artifacts match the published 0.3.0 contract. On merge this auto-publishes
@moonlight/moonlight-sdk@0.10.0to JSR; consumers (provider-platform, pay-platform, local-dev) then bump to^0.10.0.