Skip to content

ci(npm-random-beacon): pin @threshold-network/solidity-contracts to 1.2.1#3995

Open
piotr-roslaniec wants to merge 1 commit into
mainfrom
chore/pin-threshold-solidity-contracts
Open

ci(npm-random-beacon): pin @threshold-network/solidity-contracts to 1.2.1#3995
piotr-roslaniec wants to merge 1 commit into
mainfrom
chore/pin-threshold-solidity-contracts

Conversation

@piotr-roslaniec
Copy link
Copy Markdown
Collaborator

@piotr-roslaniec piotr-roslaniec commented May 24, 2026

Summary

  • The NPM Random Beacon workflow has been failing on main since the @threshold-network/solidity-contracts development dist-tag jumped from 1.3.0-dev.11 to 1.3.0-dev.16.
  • In 1.3.0-dev.16 upstream refactored TokenStaking so approveApplication is no longer exposed by the deployed ABI, causing deploy/05_approve_random_beacon_in_token_staking.ts to error out with:
    Error: No method named "approveApplication" on contract deployed as "TokenStaking"
    
  • This PR pins the upgrade step to @threshold-network/solidity-contracts@1.3.0-dev.11 — the exact version used by the last successful @keep-network/random-beacon publish (2.1.0-dev.18). Unpinning should be done in a follow-up once the deploy scripts (and the Go ABI bindings in pkg/chain/ethereum/threshold/gen/) are migrated to the new TokenStaking API.

Test plan

  • Workflow run on this branch (via workflow_dispatch) succeeds at the Deploy contracts step
  • After merge, the NPM Random Beacon workflow on main is green

….2.1

The `development` dist-tag was bumped to 1.3.0-dev.16, which refactored
`TokenStaking` so `approveApplication` is no longer exposed by the
deployed ABI. The deploy script
`solidity/random-beacon/deploy/05_approve_random_beacon_in_token_staking.ts`
calls that function and fails the CI publish step.

Pin to the last compatible version (1.2.1) so publishes succeed while
the deploy scripts and Go ABI bindings are migrated to the 1.3 API in
a separate PR.
@piotr-roslaniec piotr-roslaniec force-pushed the chore/pin-threshold-solidity-contracts branch from 94d69cb to 25f64f7 Compare May 24, 2026 06:59
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.

1 participant