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
It seems that even though the lerna publish --canary release is releasing all packages under dev versions for e.e dev.2+0fea7126d8, with the correct linked dependencies, for e.g. of installed lodestar-cli ( npm install @chainsafe/[email protected]+0fea7126d8):
This is breaking nightly release where there are breaking changes between cli and config but more importantly, the old minor release code is being bundled with the latest dev cli which is supposed to refer the latest code of other packages.
Steps to repro:
do npm install @chainsafe/[email protected]+0fea7126d8
and inspect the package-lock.json
Expected:
The resolved versions of the other lodestar- monorepo packages should exactly match the resolved cli version
The text was updated successfully, but these errors were encountered:
It seems that even though the lerna publish --canary release is releasing all packages under dev versions for e.e
dev.2+0fea7126d8
, with the correct linked dependencies, for e.g. of installedlodestar-cli
(npm install @chainsafe/[email protected]+0fea7126d8
):But
npm install
is resolving/installing the otherlodestar-*
monorepo packages of0.34.0
version:(from generated package-lock.json)
This is breaking nightly release where there are breaking changes between
cli
andconfig
but more importantly, the old minor release code is being bundled with the latest devcli
which is supposed to refer the latest code of other packages.Steps to repro:
do
npm install @chainsafe/[email protected]+0fea7126d8
and inspect the
package-lock.json
Expected:
The resolved versions of the other
lodestar-
monorepo packages should exactly match the resolvedcli
versionThe text was updated successfully, but these errors were encountered: