DO NOT MERGE wtf(yarn.lock)!: yarn.lock changes just from running "yarn"

erights commented 4 months ago

closes: #XXXX refs: https://github.com/endojs/endo/issues/2175

Description

I get these changes just from running "yarn" in a clean master

For dependencies execa, get-stream, human-signals, and signal-exit, it looks like it is adding a new version in addition to the version that it still lists. This is unpleasant. I would prefer to minimize such cases of cross-version co-existence in the same repository.

Reviewers, please let me know if these changes should be committed. If so, I'll turn this in a trivial R4R PR and close #2175

Security Considerations

Scaling Considerations

Documentation Considerations

Testing Considerations

Compatibility Considerations

Upgrade Considerations

[ ] Includes *BREAKING*: in the commit message with migration instructions for any breaking change.
[ ] Updates NEWS.md for user-facing changes.

kriskowal commented 4 months ago

Dup #2172

erights commented 4 months ago

Closing in favor of https://github.com/endojs/endo/pull/2172

endojs / endo