DO NOT MERGE: what if we rebuild yarn.lock experiment

[erights]

Just seeing what happens if we delete yarn.lock and then rebuild it, in order to detect some future compat problems.

Also uses the following directive to depend on the endo branch from endojs/endo#1630 , which is the same experiment at the endo level.

#endo-branch: markm-fresh-dep-experiment-only

See also #7937

[michaelfig]

This PR is currently tripping up all the careful CI validation that nothing in yarn.lock changes during running a yarn install and build. Maybe try running a top-level yarn install locally and see what differences it introduces.

[erights]

This PR is currently tripping up all the careful CI validation that nothing in yarn.lock changes during running a yarn install and build. Maybe try running a top-level yarn install locally and see what differences it introduces.

I don't see any changes. Did I understand your suggested experiment correctly?

agoric-sdk(master)$ git checkout markm-fresh-dep-experiment-only
Switched to branch 'markm-fresh-dep-experiment-only'
Your branch is up to date with 'origin/markm-fresh-dep-experiment-only'.

agoric-sdk(markm-fresh-dep-experiment-only)$ yarn install
yarn install v1.22.19
[1/5] 🔍  Validating package.json...
[2/5] 🔍  Resolving packages...
success Already up-to-date.
$ patch-package
patch-package 6.5.1
Applying patches...
@agoric/[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔
✨  Done in 2.71s.

agoric-sdk(markm-fresh-dep-experiment-only)$ git status
On branch markm-fresh-dep-experiment-only
Your branch is up to date with 'origin/markm-fresh-dep-experiment-only'.

nothing to commit, working tree clean

agoric-sdk(markm-fresh-dep-experiment-only)$ 

[michaelfig]

I don't see any changes. Did I understand your suggested experiment correctly?

OIC, I think the failures were stale runs before your latest commit because your branch is out-of-date (which prevents CI from running again).

Or maybe not. I'm confused. 😕

[erights]

@michaelfig I rebased on recent master, yarn installed and push --forced. I am now getting different and fewer errors, that are likely also more relevant. Thanks!