Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Don't use npm update before publication
In our projects we use `npm update` to resolve latest versions for prerelease packages from `@keep-network` scope that the current project depends on. In case of `sortition-pools` there are no dependencies to any contracts so we don't need to use `npm update`. What plain `npm update` did was updating all the packages we defined in dependencies that could cause problems as we were testing agains specific versions locked in package-lock and also CI executed it's tests agains them but here at the very last step before package publication we updated locked versions. If we need to update contracts dependencies in prerelease cycle we should specify which packages we want to update, e.g. `npm update @keep-network/sortition-pools`.
- Loading branch information