Use range in the t-network solidity-contracts dependency

We tried using `development` tag to always point to the latest development package, but that was causing `An unexpected error occurred: "expected manifest".` error when running `yarn upgrade @threshold-network/solidity-contracts`. So we're going back to using the version range. We may use `development` tag in the future, once we figure out the reason behind the error that we were getting. It is possible that the error was related to this issue: yarnpkg/yarn#4731.
keep-network · May 12, 2022 · 800087e · 800087e
1 parent 8c7e24e
commit 800087e
Show file tree

Hide file tree

Showing 2 changed files with 226 additions and 138 deletions.
diff --git a/solidity/ecdsa/package.json b/solidity/ecdsa/package.json
@@ -69,7 +69,7 @@
     "@keep-network/random-beacon": "development",
     "@keep-network/sortition-pools": "^2.0.0-pre.9",
     "@openzeppelin/contracts-upgradeable": "~4.6.0",
-    "@threshold-network/solidity-contracts": "development"
+    "@threshold-network/solidity-contracts": ">1.2.0-dev <1.2.0-ropsten"
   },
   "engines": {
     "node": ">= 14.0.0"