[Bug?]: TS patch checksum inconsistency on different computers

[thorn0]

Self-service

• I'd be willing to implement a fix

Describe the bug

Our project uses Yarn 4.0.2. On one of my computers with Windows 10, running yarn to install dependencies leads to a change in yarn.lock:

 "typescript@patch:typescript@npm%3A5.3.2#optional!builtin<compat/typescript>":
   version: 5.3.2
-  resolution: "typescript@patch:typescript@npm%3A5.3.2#optional!builtin<compat/typescript>::version=5.3.2&hash=29ae49"
+  resolution: "typescript@patch:typescript@npm%3A5.3.2#optional!builtin<compat/typescript>::version=5.3.2&hash=e012d7"
   bin:
     tsc: bin/tsc
     tsserver: bin/tsserver
-  checksum: c81b9bd20c6dbe90fa43e876c586021447f2b47baede9fa542b1f56715835c043e23b2eaf19c42c067cc6f5ae512bd9a9be28a67b3a1d9807f8c9cfb1269875e
+  checksum: 73c8bad74e732d93211c9d77f28b03307e2f5fc6a0afc73f4b783261ab567686a16d6ae958bdaef383a00be1b0b8c8b6741dd6ca3d13af4963fa7e47456d49c7
   languageName: node
   linkType: hard

However, this doesn't happen for my coworkers and on my other PC (Windows 10 too).

To reproduce

No idea how to reproduce, sorry.

Environment

System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
  Binaries:
    Node: 20.10.0 - ~\AppData\Local\Temp\xfs-9c84ca9a\node.CMD
    Yarn: 4.0.2 - ~\AppData\Local\Temp\xfs-9c84ca9a\yarn.CMD
    npm: 10.2.3 - C:\Program Files\nodejs\npm.CMD

Additional context

See also #5575

[thorn0]

Oops. Now reproduces on the other PC too. I guess I just had to run yarn after updating to 4.0.2 and I didn't.