Package
deploy
, contracts-core
, contracts-bridge
, contracts-router
Describe the feature you would like
need to design how we will handle versioning between contracts-core
, contracts-bridge
, contracts-router
, and deploy
packages
As the contract code changes, the deploy script must sometimes also change (namely, if constructor / initialize / setup function interfaces change)
However, these packages are used in different places which each have different needs
Use cases:
- production deploys: always want to deploy from tagged contract version
- development + staging deploys: probably want to deploy from tagged contract version?
- local environment testing: by default, want the local workspace version; may also want to be able to choose tagged versions too
We cannot just update the package.json
of deploy package to choose which contracts to use, as we also need to use the right version of the deploy package itself
Additional context
Relevant: all comments / discussion on this PR: https://github.com/nomad-xyz/monorepo/pull/312
help wanted typescript