Closed erights closed 9 months ago
The changes in this PR were generated by yarn
on master before #1890 was merged into master. After merging and then rebasing this PR on master, yarn
does not make any further changes to yarn.lock
, validating that these yarn.lock
changes are independent of #1890
it would be good to understand what changed on master to cause these.
Likely some PR that didn't include all related yarn.lock
changes (or a rebase gone wrong). I'd recommend endo has a porcelain check like agoric-sdk does.
closes: #XXXX refs: https://github.com/endojs/endo/pull/1890#issuecomment-1850865983
Description
At https://github.com/endojs/endo/pull/1890#issuecomment-1850865983 @kriskowal writes
Indeed, this PR is a result of running
yarn
on current endo master, and seems to reproduce the same changes. I do not offer my own opinion on whether these changes are correct, and depend fully on my reviewers.Security Considerations
yarn.lock
changes can potentially introduce and/or repair security vulnerabilities. I have no idea if this PR does either or both.Scaling Considerations
None
Documentation Considerations
Likely none.
Testing Considerations
Likely none.
Upgrade Considerations
Given that these changes surprised @kriskowal , it would be good to understand what changed on master to cause these.