Conversation
Try to fix gh actions Remove GitHub buffer dependency Not needed since there is no WASM REPL. If it was needed it should point to an Atlassian repository. Fix lockfile remove install-state from vcs Point everything at NPMJS instead of packages.atlassian.com Point everything at NPMJS instead of packages.atlassian.com Fix hardened installs Fix typescript errors Run prettier against yarnrc Fix install state Fixes
|
📊 Type Coverage ReportCoverage Comparison
Files with Most Type Issues (Top 15)
This report was generated by the Type Coverage GitHub Action |
|
@marcins Have you validated that the changesets release handles this correctly? |
- Add patch to call yarn npm publish for changesets
|
Thank you for your submission! Like many open source projects, we ask that you sign our CLA (Contributor License Agreement) before we can accept your contribution. Already signed the CLA? To re-check, try refreshing the page. |
📊 Benchmark Results✅ No significant performance changes detected. 📊 Benchmark ResultsOverall Performance
🔍 Detailed Phase AnalysisThree.js Real Repository (JS)
Three.js Real Repository (V3)
💾 Unified Memory AnalysisThree.js Real Repository (JS) Memory Statistics
Sample Counts: JS: 14, Native: 252 Three.js Real Repository (V3) Memory Statistics
Sample Counts: JS: 14, Native: 248 🖥️ Environment
|
Motivation
Apart from slightly faster
yarn installspeeds, the main benefit for us to upgrading to Yarn v4 is that we can useworkspace:*dependencies inpackage.jsonfiles, which simplifies dependency management (especially for "big" PRs when there's a release on the main branch to merge in).Changes
The bulk of the change is changing explicit versions of workspace dependencies in
package.jsontoworkspace:*.Checklist
docs/folder[no-changeset]: No functional changes