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 an outdated dependency on one of our own packages. Usually lerna auto-updates them at release creation time but this one might've been skipped due to a bug or someone accidentally committed it after a difficult rebase and the reviewers missed it.
To Reproduce
Do a search for "0.6.0"
Expected behavior
All the sibling package dependencies should be locked down to the current release which at the moment of this writing is 1.0.0-rc.2
Screenshots
Hyperledger Cactus release version or commit (git rev-parse --short HEAD):
1.0.0-rc.2
Additional context
This was discovered during work done on the jest migration co-existence branch.
The text was updated successfully, but these errors were encountered:
…dger-cacti#1532
This might be the cause of some very strange errors that the configure
script has been experiencing lately (also might be a completely benign
bug but we'll see, it needed to be fixed either way).
As a follow-up to this an automated check should be made in the CI which
verifies every dependency declaration in all package.json files to be
referring to the latest and greatest version when pulling in sibling
packages as dependencies.
Fixeshyperledger-cacti#1532
Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
…dger-cacti#1532
This might be the cause of some very strange errors that the configure
script has been experiencing lately (also might be a completely benign
bug but we'll see, it needed to be fixed either way).
As a follow-up to this an automated check should be made in the CI which
verifies every dependency declaration in all package.json files to be
referring to the latest and greatest version when pulling in sibling
packages as dependencies.
Fixeshyperledger-cacti#1532
Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
This might be the cause of some very strange errors that the configure
script has been experiencing lately (also might be a completely benign
bug but we'll see, it needed to be fixed either way).
As a follow-up to this an automated check should be made in the CI which
verifies every dependency declaration in all package.json files to be
referring to the latest and greatest version when pulling in sibling
packages as dependencies.
Fixes#1532
Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
Describe the bug
We have an outdated dependency on one of our own packages. Usually lerna auto-updates them at release creation time but this one might've been skipped due to a bug or someone accidentally committed it after a difficult rebase and the reviewers missed it.
To Reproduce
Do a search for
"0.6.0"
Expected behavior
All the sibling package dependencies should be locked down to the current release which at the moment of this writing is
1.0.0-rc.2
Screenshots
Hyperledger Cactus release version or commit (git rev-parse --short HEAD):
1.0.0-rc.2
Additional context
This was discovered during work done on the jest migration co-existence branch.
The text was updated successfully, but these errors were encountered: