Repository navigation
Revert "lookup: temporarily use head for jest" - #901
Conversation
This reverts commit 479d799.
It seems that a new commit is always necessary to fix the lockfile after a release: If we remove |
|
😅 From yarnpkg/berry#3486 (comment) we can probably pass We need the extra commit as we cannot use |
Co-authored-by: Michaël Zasso <[email protected]>
|
Ah jeez, we've broken the |
|
28.0.2 is out with the above fix. Can you re-trigger? 🤞 |
|
Thanks for looking into it. I've rerun (using this branch of I could also reproduce locally with |
|
Ah, nice! It's the result of |
|
I can also reproduce locally with:
Same error and stack. |
|
Aha - |
|
Running "build:js" before "remove-examples" works for me. |
Is that not what Line 266 in d3dedd0 Is the issue that install is run before |
|
Here's the result of Details |
|
Ah, I thought the installation of the examples failed. If it's just running the tests then we can change the order As for the failing test, sounds like an issue with symlinks |
Co-authored-by: Simen Bekkhus <[email protected]>
|
Looks like it passed? 🥳 |
|
Land it? 😀 |
|
Would someone in @nodejs/citgm mind landing this? (I guess I should request to be added to that team.) |
We could also add this repository to the list in nodejs/Release#557 and grant all releasers maintain access? |
|
Thanks, folks! Happy that Jest is green on CITGM again. We do lots of weird stuff, good to get notice as early as possible about compat issues 😀 |

Reverts #899
It seems Jest failing under CITGM on all platforms with v28.0.1 (peerDeps related?)