You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have the WalletRegistryStub contract. This contract lands in the @development NPM package and is used by the client to generate bindings when running make all. The additional functionalities of the stub, forceAddWallet and getDkgData, are used only in unit tests of solidity/ecdsa.
The problem
We have the
WalletRegistryStub
contract. This contract lands in the@development
NPM package and is used by the client to generate bindings when runningmake all
. The additional functionalities of the stub,forceAddWalle
t andgetDkgData
, are used only in unit tests ofsolidity/ecdsa
.The context
We have two deployment scripts defined:
keep-core/solidity/ecdsa/package.json
Lines 31 to 32 in 0484ddb
deploy:test
is used in tests and deploys theWalletRegistryStub
with additional functions.deploy
is used in regular deployments. For example:keep-core/.github/workflows/contracts-ecdsa.yml
Line 328 in 0484ddb
For some reason, we decided to use
deploy:test
for the development NPM package publication:keep-core/.github/workflows/npm-ecdsa.yml
Lines 40 to 43 in 0484ddb
That's why
WalletRegistryStub
gets into the@development
package.The solution
Having
@development
as adeploy
frommain
(with no stubs) makes more sense.deploy:test
should only be used for tests.Tasks
The text was updated successfully, but these errors were encountered: