build(deps): update package.json to lerna@8#11503
Conversation
Deploying agoric-sdk with
|
| Latest commit: |
e5dbd25
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://f969aaf7.agoric-sdk.pages.dev |
| Branch Preview URL: | https://mfig-npm-publish.agoric-sdk.pages.dev |
77e6d25 to
3876437
Compare
This version of Lerna is necessary to replace `"workspace:*"` version specifiers with the actual version numbers of the dependencies when `lerna publish` is used. Without this change, the published NPM packages are unusable.
3876437 to
fd6131f
Compare
| "moddable/modules/data/**", | ||
| "moddable/xs/includes/**", | ||
| "moddable/xs/makefiles/**", | ||
| "moddable/xs/sources/**", |
There was a problem hiding this comment.
Interesting. This is apropos of Lerna? Npm pack was forgiving.
There was a problem hiding this comment.
Yeah, when testing the viability of the packages, I noticed the missing files from these subtrees. I think this was fixed a few times by other PRs that never merged.
There was a problem hiding this comment.
I think we had some tool / script somewhere allowing us to check if there were any differences in files included in an npm package. I'm really curious why this would now have changed.
| const { stdout: npmout } = await $`npm pack --json`; | ||
| const [{ filename }] = JSON.parse(npmout); | ||
| const filename = join(tmp, 'package.tgz'); | ||
| await $`yarn pack --out ${filename}`; |
There was a problem hiding this comment.
Ah, because yarn will account for the workspace protocol and npm will not. Thanks. Also nice that we can specify and don’t have to parse out the filename.
|
This pull request has been removed from the queue for the following reason: The merge conditions cannot be satisfied due to failing checks: You can check the last failing draft PR here: #11648. You may have to fix your CI before adding the pull request to the queue again. |
Looks like `lint-primary` is suffering from timeouts, probably due to excessive work being done by `tsc`.
31338d3 to
e5dbd25
Compare
|
This pull request has been removed from the queue for the following reason: The merge conditions cannot be satisfied due to failing checks: You can check the last failing draft PR here: #11650. You may have to fix your CI before adding the pull request to the queue again. |
|
@Mergifyio requeue |
✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically |
|
This pull request has been removed from the queue for the following reason: The merge conditions cannot be satisfied due to failing checks: You can check the last failing draft PR here: #11652. You may have to fix your CI before adding the pull request to the queue again. |
mhofman
left a comment
There was a problem hiding this comment.
I have verified that the newly published dev versions correctly rewrite the workspace: dependencies.
| "moddable/modules/data/**", | ||
| "moddable/xs/includes/**", | ||
| "moddable/xs/makefiles/**", | ||
| "moddable/xs/sources/**", |
There was a problem hiding this comment.
I think we had some tool / script somewhere allowing us to check if there were any differences in files included in an npm package. I'm really curious why this would now have changed.
There was a problem hiding this comment.
What is the behavior of the new lerna regarding pre-releases? We are using pre-releases tags currently both for dev packages and for our "release" versions.
There was a problem hiding this comment.
We do have a test that verifies that npm pack works. That test switched to using yarn pack in this change, which probably accounts for the difference in requirements. Presumably, lerna drives yarn pack.
There was a problem hiding this comment.
I don't think what pack command we uses changes anything to my question, which was specifically how lerna generated the new version depending on whether it was a pre-release or not. Seeing #11655, in lerna 8, the semantics of bumping version for 0.x were dependent on whether it was a pre-release or not, which seems misguided.
refs: #11503, #11664 ## Description Solve abysmal [perf issues on macOS (#11664)](#11664) found in `lerna-8` by using `@lerna-lite` instead. Also, apply the patch as described in [comments](https://github.com/Agoric/agoric-sdk/pull/11503/files#r2227087619) after the [lerna-8 upgrade PR #11503](#11503) landed. ### Security Considerations CI and release management only. ### Scaling Considerations n/a ### Documentation Considerations n/a ### Testing Considerations CI ### Upgrade Considerations Relying on a more maintained package.
closes: #11598
Description
Update our version of Lerna.
Security Considerations
Same considerations as any package version upgrade.
Scaling Considerations
Only used during CI and NPM release process.
Documentation Considerations
n/a
Testing Considerations
n/a
Upgrade Considerations
Maintainer use only.