{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":148228732,"defaultBranch":"master","name":"berry","ownerLogin":"yarnpkg","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2018-09-10T22:49:22.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/22247014?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1715505651.0","currentOid":""},"activityList":{"items":[{"before":"bfa6489467e0e11ee87268e01e38e4f7e8d4d4b0","after":"cdb7f3c9ca370a574f0bb46242db0291f255ac5c","ref":"refs/heads/master","pushedAt":"2024-06-01T19:30:13.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"arcanis","name":"Maël Nison","path":"/arcanis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1037931?s=80&v=4"},"commit":{"message":"Remove \"sherlock\" from bug report template (#6306)\n\nThe linked documentation doesn't exist anymore.\r\nThe associated website for the tool [1] shows some useful information,\r\nbut (IMHO) it's unclear to see how to apply it in a fresh repo.\r\n\r\nAdditionally, `arcanis` mentioned in a comment here [2] that perhaps it\r\nshould be removed since it's not often used and the playground is\r\nbroken.\r\n\r\nFixes #5837\r\nFixes #5950\r\n\r\n[1] https://github.com/arcanis/sherlock\r\n[2] https://github.com/yarnpkg/berry/pull/6139#issuecomment-1977286294\r\n\r\n\r\n## Checklist\r\n\r\n\r\n\r\n\r\n- [x] I have read the [Contributing\r\nGuide](https://yarnpkg.com/advanced/contributing).\r\n\r\n\r\n\r\n- [x] I have set the packages that need to be released for my changes to\r\nbe effective.\r\n\r\n\r\n\r\n- [x] I will check that all automated PR checks pass before the PR gets\r\nreviewed.","shortMessageHtmlLink":"Remove \"sherlock\" from bug report template (#6306)"}},{"before":"85041726631c07126cef12661739939e9e90d709","after":"bfa6489467e0e11ee87268e01e38e4f7e8d4d4b0","ref":"refs/heads/master","pushedAt":"2024-05-17T10:47:27.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"arcanis","name":"Maël Nison","path":"/arcanis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1037931?s=80&v=4"},"commit":{"message":"Rework peer requirement and warning system (#6205)\n\n**What's the problem this PR addresses?**\r\n\r\nThere are a number of issues with the current peer requirement and peer\r\nwarning system:\r\n\r\n----\r\n\r\nFirstly, since v4, we lost the ability to list all peer requirements in\r\nthe project and to explain missing peer dependency warnings, which is a\r\nhuge degradation to DX.\r\n\r\n----\r\n\r\nSecondly, also since v4, transitive peer warnings are no longer\r\ndisplayed. The rationale given was \"those are not actionable\". But they\r\n*are* actionable because we have `packageExtensions`.\r\n\r\nMore importantly, there are no indication nor discoverability when this\r\nhappens. Yarn exits without even a warning when transitive peer warnings\r\ncan put the project in an invalid state. Even when the user somehow\r\nknows that there are transitive peer warnings, they are impossible to\r\ninvestigate and fix without the proper tools.\r\n\r\n----\r\n\r\nThirdly, as I just reported, the peer warning aggregation is aggregating\r\nunrelated peer requests, causing `yarn explain peer-requirements` to\r\ngive incorrect advice. #6203\r\n\r\n----\r\n\r\nFinally, the peer resolution pipeline has been refactored and added to\r\nmany times over the years which make the code quite difficult to\r\nunderstand. This is compounded by misplaced comments and overloading\r\nterms like \"peer descriptor\" in the code.\r\n\r\n----\r\n\r\nCloses #5841\r\nCloses #5977\r\nCloses #6016\r\nCloses #6118\r\nCloses #6203\r\n\r\n\r\n**How did you fix it?**\r\n\r\nOn the last problem, it is quite impossible to completely solve in one\r\ngo, so I only took small bites and at least rewrote some of the comments\r\nto better capture the current peer pipeline. I have also unified the\r\nterminology and change variable names to use those terminology to reduce\r\nambiguity. Maybe we should add these to the lexicon?\r\n\r\nLet's say\r\n- Package `A` (regular-)depends on `B`, which peer-depends on `C`\r\n- Package `A` also depends on `C`\r\n\r\n```\r\nA@1.0.0 --> B@^1.0.0 (resolves to B@1.1.0) ==> C@^1.0.0\r\n --> C@^1.2.0 (resolves to C@1.3.0)\r\n```\r\n\r\nIn the scope of this single level\r\n- The package `A@1.0.0` is known as the **subject** or **requestee**\r\n- The package `B@1.1.0` is known as the **requester**. Also called the\r\n**virtualized package** in the code because of what the pipeline is\r\ndoing\r\n- The ident `C` is known as the **peer ident** and the descriptor\r\n`C@^1.0.0` is known as the **peer descriptor**\r\n- The descriptor `C@^1.2.0` is the **provided descriptor**. Similarly,\r\n`C@1.3.0` is the **provided locator/package**. **Provision** can refer\r\nto any of those depending on context.\r\n- Note that the provision is not necessarily `A`'s dependency. `A`\r\nitself could be used if its ident *were* matching, or a package can be\r\nnot provided at all.\r\n\r\nBased on those we can create some composite data structures:\r\n- A **peer request** encapsulates a requester + peer ident.\r\n- If a subject does not provide to the request itself, but instead\r\nrequests a peer dependency under the same ident, that subject and the\r\nnew peer request it issues are both said to **forward** the original\r\npeer request.\r\n- A **peer requirement** encapsulates a subject + peer ident + one or\r\nmore peer requests. This captures the fact that a single subject that\r\ndepends on multiple peer requesters can satisfy multiple peer requests\r\nat the same time\r\n- Note that peer requests and peer requirements is a many-to-many\r\nrelationship. A peer request is included in multiple peer requirements\r\nif the requester is depended upon multiple times (which can happen due\r\nto deduplication).\r\n- A peer requirement is said to be a **root peer requirement** if the\r\nsubject does not forward the peer requests.\r\n\r\n----\r\n\r\nWith those concepts established, the core of this PR changes the peer\r\nrequirement and peer warning system to use a tree-based structure. The\r\nnodes of the tree are either peer requests or peer requirements. A peer\r\nrequest's children are the requests it forwards, and a peer\r\nrequirement's children are the requests it includes. Note that a tree\r\ncan only ever include peer requirements and requests regarding a single\r\npeer ident.\r\n\r\n![Untitled\r\nDiagram](https://github.com/yarnpkg/berry/assets/41266433/166595b0-b7be-4e8c-a589-64a7d16ac462)\r\n\r\nBy storing all peer requirement nodes in `Project`, other places can\r\neasily display information on peer requirements/requests/warnings by\r\nretrieving them form the tree (using the new tree-view UI, even). This\r\nallows us to reimplement `yarn explain peer-requirements` and `yarn\r\nexplain peer-requirements ` to list all requirements and explain\r\nany peer requirement (even without warnings) respectively. This also\r\nfixes #6203 because the peer requirement nodes correctly group the peer\r\nrequests.\r\n\r\n\r\n![image](https://github.com/yarnpkg/berry/assets/41266433/7f40f8f3-53da-48d4-bb10-38a8c23ccec4)\r\n\r\n----\r\n\r\nTo solve the discoverability problem without bringing back the clutter,\r\nI've added an additional CTA for transitive peer warnings, so all\r\ntransitive peer warnings are reduced to a single line.\r\n\r\n```\r\n➤ YN0000: ┌ Post-resolution validation\r\n➤ YN0002: │ workspace-b@workspace:workspace-b doesn't provide p (p427bb), requested by y.\r\n➤ YN0086: │ Some peer dependencies are incorrectly met by your project; run yarn explain peer-requirements for details, where is the six-letter p-prefixed code.\r\n➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.\r\n➤ YN0000: └ Completed\r\n```\r\n\r\nA user wishing to view the transitive warnings can do so with the\r\nreimplemented `yarn explain peer-requirements` command.\r\n\r\n----\r\n\r\nLastly, I don't know how much of the original peer requirement and\r\nwarning system matter for BC. For now, I have recreated the data\r\nstructures created by the original system, except the aggregated\r\nwarnings which is the wrong abstraction as noted. I have added TODO\r\ncomments to remove those code for the next major. Please advice if the\r\noriginal system can be safely removed in a minor.\r\n\r\n**Checklist**\r\n\r\n\r\n\r\n- [x] I have read the [Contributing\r\nGuide](https://yarnpkg.com/advanced/contributing).\r\n\r\n\r\n\r\n- [x] I have set the packages that need to be released for my changes to\r\nbe effective.\r\n\r\n\r\n\r\n- [x] I will check that all automated PR checks pass before the PR gets\r\nreviewed.\r\n\r\n---------\r\n\r\nCo-authored-by: Maël Nison ","shortMessageHtmlLink":"Rework peer requirement and warning system (#6205)"}},{"before":"e4687c90a277c9484ae5ea3df37775e3d70cc7d8","after":null,"ref":"refs/heads/mael/test-binary","pushedAt":"2024-05-12T09:20:51.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"arcanis","name":"Maël Nison","path":"/arcanis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1037931?s=80&v=4"}},{"before":"3415a677051b56e67f8bf2aee0753bf1ea9aa890","after":"85041726631c07126cef12661739939e9e90d709","ref":"refs/heads/master","pushedAt":"2024-05-12T09:20:50.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"arcanis","name":"Maël Nison","path":"/arcanis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1037931?s=80&v=4"},"commit":{"message":"Adds TEST_BINARY (#6291)\n\n## What's the problem this PR addresses?\r\n\r\nI want to run the tests on an alternate Yarn build.\r\n\r\n## How did you fix it?\r\n\r\nReplaces the TEST_FROM_SOURCES environment variable by a more flexible\r\nTEST_BINARY which lets us select any binary on disk to run the tests.\r\n\r\n## Checklist\r\n\r\n\r\n\r\n\r\n- [x] I have read the [Contributing\r\nGuide](https://yarnpkg.com/advanced/contributing).\r\n\r\n\r\n\r\n- [x] I have set the packages that need to be released for my changes to\r\nbe effective.\r\n\r\n\r\n\r\n- [x] I will check that all automated PR checks pass before the PR gets\r\nreviewed.","shortMessageHtmlLink":"Adds TEST_BINARY (#6291)"}},{"before":null,"after":"e4687c90a277c9484ae5ea3df37775e3d70cc7d8","ref":"refs/heads/mael/test-binary","pushedAt":"2024-05-12T09:13:25.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"arcanis","name":"Maël Nison","path":"/arcanis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1037931?s=80&v=4"},"commit":{"message":"Adds TEST_BINARY","shortMessageHtmlLink":"Adds TEST_BINARY"}},{"before":"cdc542ab296ea1b4edf85b713e0e91b24f742586","after":"866e929b5f41404b6002adbda00e33c82f8f2266","ref":"refs/heads/cherry-pick/next-release","pushedAt":"2024-05-08T18:15:33.000Z","pushType":"push","commitsCount":6,"pusher":{"login":"merceyz","name":"Kristoffer K.","path":"/merceyz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3842800?s=80&v=4"},"commit":{"message":"ci(e2e): remove gatsby development server test (#6084)\n\n**What's the problem this PR addresses?**\r\n\r\nThe Gatsby development server test has been timing out in the CI for\r\nmonths now, though it passes locally.\r\n\r\n**How did you fix it?**\r\n\r\nDisable to so we notice when the build stops working.\r\n\r\n**Checklist**\r\n- [x] I have read the [Contributing\r\nGuide](https://yarnpkg.com/advanced/contributing).\r\n- [x] I have set the packages that need to be released for my changes to\r\nbe effective.\r\n- [x] I will check that all automated PR checks pass before the PR gets\r\nreviewed.","shortMessageHtmlLink":"ci(e2e): remove gatsby development server test (#6084)"}},{"before":"450097c303ab0247f131291ed6916bffaa42d5f8","after":"cdc542ab296ea1b4edf85b713e0e91b24f742586","ref":"refs/heads/cherry-pick/next-release","pushedAt":"2024-05-08T18:04:19.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"merceyz","name":"Kristoffer K.","path":"/merceyz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3842800?s=80&v=4"},"commit":{"message":"ci: test more Node.js versions","shortMessageHtmlLink":"ci: test more Node.js versions"}},{"before":"effc932614d5351bbfeed8e0e6aa4b2c6c52821d","after":"3415a677051b56e67f8bf2aee0753bf1ea9aa890","ref":"refs/heads/master","pushedAt":"2024-05-08T17:50:45.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"yarnbot","name":"Friendly Yarn Bot","path":"/yarnbot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/50545563?s=80&v=4"},"commit":{"message":"Sync master with the changes from master","shortMessageHtmlLink":"Sync master with the changes from master"}},{"before":"9b7b745fb6eb928e909df23200d9860f8803f836","after":"effc932614d5351bbfeed8e0e6aa4b2c6c52821d","ref":"refs/heads/master","pushedAt":"2024-05-08T17:48:50.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"yarnbot","name":"Friendly Yarn Bot","path":"/yarnbot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/50545563?s=80&v=4"},"commit":{"message":"Releasing 7 new packages\n\n| Package name | Version |\n| --- | --- |\n| `@yarnpkg/cli` | `4.2.2` |\n| `@yarnpkg/plugin-pnp` | `4.0.5` |\n| `@yarnpkg/fslib` | `3.1.0` |\n| `@yarnpkg/libzip` | `3.1.0` |\n| `@yarnpkg/pnpify` | `4.1.0` |\n| `@yarnpkg/pnp` | `4.0.5` |\n| `@yarnpkg/plugin-essentials` | `4.1.2` |","shortMessageHtmlLink":"Releasing 7 new packages"}},{"before":"824ec90691dd99337a6918cc6ecb11519f7d1a05","after":null,"ref":"refs/heads/rdil/actions","pushedAt":"2024-05-06T20:40:46.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"arcanis","name":"Maël Nison","path":"/arcanis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1037931?s=80&v=4"}},{"before":"3a74ca9b85c68914d9f3839052ae983d0bab8170","after":"9b7b745fb6eb928e909df23200d9860f8803f836","ref":"refs/heads/master","pushedAt":"2024-05-06T20:40:45.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"arcanis","name":"Maël Nison","path":"/arcanis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1037931?s=80&v=4"},"commit":{"message":"chore: Update GitHub actions versions (#6279)\n\nSaw a bunch of warnings while checking a log, apparently these versions\r\nuse node 16 which is deprecated, and the v3 of upload-artifact and\r\ndownload-artifact will stop working in November.","shortMessageHtmlLink":"chore: Update GitHub actions versions (#6279)"}},{"before":null,"after":"824ec90691dd99337a6918cc6ecb11519f7d1a05","ref":"refs/heads/rdil/actions","pushedAt":"2024-05-06T20:26:02.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"RDIL","name":"Reece Dunham","path":"/RDIL","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34555510?s=80&v=4"},"commit":{"message":"chore: Update GitHub actions versions","shortMessageHtmlLink":"chore: Update GitHub actions versions"}},{"before":"bb59325af4d544c889a8a7c3e675f98ce50b5cd0","after":"98abfc6457d929593c05e603c54746144f87cf63","ref":"refs/heads/rdil/yn0020","pushedAt":"2024-05-06T19:57:38.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"RDIL","name":"Reece Dunham","path":"/RDIL","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34555510?s=80&v=4"},"commit":{"message":"Log where package.json is (untested)","shortMessageHtmlLink":"Log where package.json is (untested)"}},{"before":null,"after":"0cef81fe1bdc35def2c6d0e88dd44a998707661c","ref":"refs/heads/mael/eslint-flat-config-sdk","pushedAt":"2024-05-06T16:42:07.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"arcanis","name":"Maël Nison","path":"/arcanis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1037931?s=80&v=4"},"commit":{"message":"Adds sdk support for esm loaders","shortMessageHtmlLink":"Adds sdk support for esm loaders"}},{"before":"6348eea9930fd4c749a5bec71417a2ba2bed294b","after":null,"ref":"refs/heads/mael/yarn-why-fix","pushedAt":"2024-05-06T13:02:39.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"arcanis","name":"Maël Nison","path":"/arcanis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1037931?s=80&v=4"}},{"before":"96e8b3c52a2bdd3675beda57a171e64eb6fde1e6","after":"3a74ca9b85c68914d9f3839052ae983d0bab8170","ref":"refs/heads/master","pushedAt":"2024-05-06T13:02:38.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"arcanis","name":"Maël Nison","path":"/arcanis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1037931?s=80&v=4"},"commit":{"message":"Fixes `yarn why -R` (#6251)\n\n## What's the problem this PR addresses?\r\n\r\nWhen using the `-R` flag on a flag with a large amount of workspaces,\r\n`yarn why` may fail to return enough information to answer the question\r\n\"why is this package here\". This is because of a bug in the\r\nimplementation where we decline to print a package in the tree view if:\r\n\r\n- We saw it before, or\r\n- It's a workspace (because we'll print it later anyway)\r\n\r\nHowever we check the first condition first and we put the package in the\r\n\"seen\" list before we check whether it's a workspace. As a result,\r\nworkspaces that are dependencies of other workspaces won't have their\r\ndependencies shown.\r\n\r\n## How did you fix it?\r\n\r\nFlipped the two conditions.\r\n\r\n## Checklist\r\n\r\n\r\n\r\n\r\n- [x] I have read the [Contributing\r\nGuide](https://yarnpkg.com/advanced/contributing).\r\n\r\n\r\n\r\n- [x] I have set the packages that need to be released for my changes to\r\nbe effective.\r\n\r\n\r\n\r\n- [x] I will check that all automated PR checks pass before the PR gets\r\nreviewed.","shortMessageHtmlLink":"Fixes yarn why -R (#6251)"}},{"before":null,"after":"e1e80006cb1dae2fce861b253846566e06d4f7d1","ref":"refs/heads/mael/eslint-flat-config","pushedAt":"2024-05-06T12:50:28.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"arcanis","name":"Maël Nison","path":"/arcanis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1037931?s=80&v=4"},"commit":{"message":"Versions","shortMessageHtmlLink":"Versions"}},{"before":"0b1bc0273937185f7476e8b1a41f2f511fc8fb66","after":"6348eea9930fd4c749a5bec71417a2ba2bed294b","ref":"refs/heads/mael/yarn-why-fix","pushedAt":"2024-05-06T09:55:03.000Z","pushType":"push","commitsCount":19,"pusher":{"login":"arcanis","name":"Maël Nison","path":"/arcanis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1037931?s=80&v=4"},"commit":{"message":"Merge branch 'master' into mael/yarn-why-fix","shortMessageHtmlLink":"Merge branch 'master' into mael/yarn-why-fix"}},{"before":"1d56315a75b95109f760ba0b584b726e222749c8","after":"0b1bc0273937185f7476e8b1a41f2f511fc8fb66","ref":"refs/heads/mael/yarn-why-fix","pushedAt":"2024-05-06T09:35:18.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"arcanis","name":"Maël Nison","path":"/arcanis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1037931?s=80&v=4"},"commit":{"message":"Adds tests","shortMessageHtmlLink":"Adds tests"}},{"before":"762732512606511cf1693a0715a2ec4ee70a06d0","after":"96e8b3c52a2bdd3675beda57a171e64eb6fde1e6","ref":"refs/heads/master","pushedAt":"2024-05-06T08:56:32.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"arcanis","name":"Maël Nison","path":"/arcanis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1037931?s=80&v=4"},"commit":{"message":"fix: keep NODE_OPTIONS unset when the calculated value is empty (#6255)\n\nAlso update the type of the process-environment to NodeJS's, which\r\nallows undefined as valid value.\r\n\r\n## What's the problem this PR addresses?\r\n\r\nResolves #6148\r\n\r\n## How did you fix it?\r\n\r\nIf the calculated `NODE_OPTIONS` value is an empty string, set the\r\nenvironment value to `undefined`.\r\n\r\nSince the original definition of the process-environment did not allow\r\nundefined, I changed the type definition to use `NodeJS.ProcessEnv`.\r\nOtherwise the code would need to be written as\r\n\r\n```ts\r\nenv.NODE_OPTIONS = nodeOptions ? nodeOptions : undefined as unknown as string;\r\n```\r\n\r\nI haven't figured out where this could be tested, so I did not\r\nadd/update any unit tests.\r\n\r\n## Checklist\r\n\r\n- [x] I have read the [Contributing\r\nGuide](https://yarnpkg.com/advanced/contributing).\r\n- [x] I have set the packages that need to be released for my changes to\r\nbe effective.\r\n- [x] I will check that all automated PR checks pass before the PR gets\r\nreviewed.\r\n\r\n---------\r\n\r\nCo-authored-by: Maël Nison ","shortMessageHtmlLink":"fix: keep NODE_OPTIONS unset when the calculated value is empty (#6255)"}},{"before":"ebf9a0d6d1bb2d90da7eef5701e670f7a88cb323","after":"762732512606511cf1693a0715a2ec4ee70a06d0","ref":"refs/heads/master","pushedAt":"2024-05-06T08:56:04.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"arcanis","name":"Maël Nison","path":"/arcanis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1037931?s=80&v=4"},"commit":{"message":"feat(fslib): add `rmPromise`/`rmSync` methods (#6226)\n\n**What's the problem this PR addresses?**\r\n\r\n\r\n\r\nThe `recursive` option of `rmdir` is deprecated in Node.js.\r\nUnfortunately, because this lib doesn't expose the `rm` method, there's\r\nno alternative atm. This PR adds that alternative.\r\n\r\nhttps://nodejs.org/api/deprecations.html#DEP0147\r\n\r\n...\r\n\r\n**How did you fix it?**\r\n\r\n\r\nI copied the `rmdir` implementations into a `rm` equivalent methods that\r\ncalls in the `fs.rm` instead of `fs.rmdir`.\r\n...\r\n\r\n**Checklist**\r\n\r\n\r\n\r\n- [x] I have read the [Contributing\r\nGuide](https://yarnpkg.com/advanced/contributing).\r\n\r\n\r\n\r\n- [x] I have set the packages that need to be released for my changes to\r\nbe effective.\r\n\r\n\r\n\r\n- [x] I will check that all automated PR checks pass before the PR gets\r\nreviewed.\r\n\r\n---------\r\n\r\nCo-authored-by: Maël Nison ","shortMessageHtmlLink":"feat(fslib): add rmPromise/rmSync methods (#6226)"}},{"before":"0158e47a69598e4d5206f92f4e61af9fc95fbed7","after":null,"ref":"refs/heads/merceyz/fix/pnp-import-attribute","pushedAt":"2024-05-06T08:32:22.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"arcanis","name":"Maël Nison","path":"/arcanis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1037931?s=80&v=4"}},{"before":"578d8961358503ec04705d15f89284664fe1be61","after":"ebf9a0d6d1bb2d90da7eef5701e670f7a88cb323","ref":"refs/heads/master","pushedAt":"2024-05-06T08:32:21.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"arcanis","name":"Maël Nison","path":"/arcanis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1037931?s=80&v=4"},"commit":{"message":"fix(pnp): esm - support import attributes (#6268)\n\n**What's the problem this PR addresses?**\r\n\r\nIn Node.js v22 import assertions were replaced with import attributes so\r\nwe need to add support for those as well.\r\n\r\nFixes https://github.com/yarnpkg/berry/issues/6267\r\n\r\n**How did you fix it?**\r\n\r\nAdded support for the `importAttributes` property.\r\n\r\n**Checklist**\r\n- [x] I have read the [Contributing\r\nGuide](https://yarnpkg.com/advanced/contributing).\r\n- [x] I have set the packages that need to be released for my changes to\r\nbe effective.\r\n- [x] I will check that all automated PR checks pass before the PR gets\r\nreviewed.","shortMessageHtmlLink":"fix(pnp): esm - support import attributes (#6268)"}},{"before":null,"after":"bb59325af4d544c889a8a7c3e675f98ce50b5cd0","ref":"refs/heads/rdil/yn0020","pushedAt":"2024-05-03T20:59:59.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"RDIL","name":"Reece Dunham","path":"/RDIL","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34555510?s=80&v=4"},"commit":{"message":"docs: Clarify YN0020","shortMessageHtmlLink":"docs: Clarify YN0020"}},{"before":null,"after":"0158e47a69598e4d5206f92f4e61af9fc95fbed7","ref":"refs/heads/merceyz/fix/pnp-import-attribute","pushedAt":"2024-05-02T22:58:18.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"merceyz","name":"Kristoffer K.","path":"/merceyz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3842800?s=80&v=4"},"commit":{"message":"fix(pnp): support import attributes","shortMessageHtmlLink":"fix(pnp): support import attributes"}},{"before":"bf24f592eb0a7e8ac207387b0d60ea2ac7d66ebf","after":"578d8961358503ec04705d15f89284664fe1be61","ref":"refs/heads/master","pushedAt":"2024-05-02T17:51:57.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"yarnbot","name":"Friendly Yarn Bot","path":"/yarnbot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/50545563?s=80&v=4"},"commit":{"message":"Sync master with the changes from master","shortMessageHtmlLink":"Sync master with the changes from master"}},{"before":"33a8c808cd2ef7383d9d80fac825efd5ab2d83bb","after":"bf24f592eb0a7e8ac207387b0d60ea2ac7d66ebf","ref":"refs/heads/master","pushedAt":"2024-05-02T17:48:32.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"yarnbot","name":"Friendly Yarn Bot","path":"/yarnbot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/50545563?s=80&v=4"},"commit":{"message":"Releasing 13 new packages\n\n| Package name | Version |\n| --- | --- |\n| `@yarnpkg/cli` | `4.2.1` |\n| `@yarnpkg/extensions` | `2.0.3` |\n| `@yarnpkg/plugin-compat` | `4.0.5` |\n| `@yarnpkg/plugin-version` | `4.0.3` |\n| `@yarnpkg/builder` | `4.1.1` |\n| `@yarnpkg/sdks` | `3.1.2` |\n| `@yarnpkg/core` | `4.0.5` |\n| `@yarnpkg/plugin-npm-cli` | `4.0.4` |\n| `@yarnpkg/parsers` | `3.0.2` |\n| `@yarnpkg/shell` | `4.0.2` |\n| `@yarnpkg/plugin-typescript` | `4.1.1` |\n| `@yarnpkg/plugin-pnp` | `4.0.4` |\n| `@yarnpkg/pnp` | `4.0.4` |","shortMessageHtmlLink":"Releasing 13 new packages"}},{"before":"0db762b947eca8580f3fbd6569a5007f88ee26c0","after":null,"ref":"refs/heads/merceyz/build/fix-builds","pushedAt":"2024-05-02T17:40:39.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"arcanis","name":"Maël Nison","path":"/arcanis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1037931?s=80&v=4"}},{"before":"fd9b1771c88e0d76bbd8169a1f5249a03e81f37d","after":"33a8c808cd2ef7383d9d80fac825efd5ab2d83bb","ref":"refs/heads/master","pushedAt":"2024-05-02T17:40:38.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"arcanis","name":"Maël Nison","path":"/arcanis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1037931?s=80&v=4"},"commit":{"message":"build: explicitly set `noEmit: false` in the build script (#6266)\n\n**What's the problem this PR addresses?**\r\n\r\nhttps://github.com/yarnpkg/berry/pull/6133 (cc @clemyan) enabled\r\n`noEmit` by default which caused `yarn pack` to not get any build\r\noutput.\r\n\r\nFixes https://github.com/yarnpkg/berry/issues/6265\r\n\r\n**How did you fix it?**\r\n\r\nExplicitly set `noEmit: false` in the build script.\r\n\r\n**Checklist**\r\n- [x] I have read the [Contributing\r\nGuide](https://yarnpkg.com/advanced/contributing).\r\n- [x] I have set the packages that need to be released for my changes to\r\nbe effective.\r\n- [x] I will check that all automated PR checks pass before the PR gets\r\nreviewed.","shortMessageHtmlLink":"build: explicitly set noEmit: false in the build script (#6266)"}},{"before":"e53dde2d49ea93ab4a2181b3dd9f4d9490ba9466","after":"0db762b947eca8580f3fbd6569a5007f88ee26c0","ref":"refs/heads/merceyz/build/fix-builds","pushedAt":"2024-05-02T17:26:55.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"merceyz","name":"Kristoffer K.","path":"/merceyz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3842800?s=80&v=4"},"commit":{"message":"build: force disable `noEmit` instead","shortMessageHtmlLink":"build: force disable noEmit instead"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEWd3VWgA","startCursor":null,"endCursor":null}},"title":"Activity · yarnpkg/berry"}