fix: commit auto-generated yarn.lock

[erights]

closes: #XXXX
refs: #XXXX

Description

The yarn.lock changes in this PR were purely automatically generated from a clean master by running yarn. No other changes.

Security Considerations

Scaling Considerations

Documentation Considerations

Testing Considerations

Upgrade Considerations

[kriskowal]

This is suspicious. It suggests that something has a package.json that is pinned to a version of this package that is not in the workspace.

I would like to try this alternative and see whether package.jsons change or yarn.lock changes.

> ./scripts/get-versions.sh . | ./scripts/set-versions.sh
> yarn

[erights]

Looks the same after starting over from a fresh master and then running those two commands.

[kriskowal]

I would like to investigate these changes more deeply.

[kriskowal]

I’ve reproduced these yarn.lock changes locally and also executed the commands I recommended above and found no changes to package.json, so I am perplexed. Stay tuned.

[kriskowal]

Figured it out. The problem is that Jessie.js is out of sync.

[kriskowal]

Let’s land this since it at least makes sense that Jessie needs older versions. I’m separately getting Jessie in sync, which will undo these changes. endojs/Jessie#113