Mike McCready

@ms-ati I took a quick look at the potential size savings by removing Yarn v1 Classic: | Image | uncompressed | uncompressed no Yarn | savings MB | savings %...

@ms-ati > Q: Should we consider creating a named image variant which stops installing Yarn? This would have the potential to double the number of new images built for every...

If the source repo for Yarn v1 Classic, https://github.com/yarnpkg/yarn, is cloned locally then CI tests and a vulnerability audit are run, then these are the results: ## Test results ```text...

Given the abandoned state of Yarn v1 Classic (last update [v1.22.22](https://github.com/yarnpkg/yarn/releases/tag/v1.22.22) 18 months ago) it seems like there ought to be an exception process needing approval to continue to distribute...

Withdrawing this enhancement suggestion, as there was no response. Keys for signers of Node.js releases will need to be manually maintained as before. The set of keys does however not...

I re-opened this issue due to @richardlau's https://github.com/nodejs/node/issues/61022#issuecomment-3642346288 which said: > This has [affected unofficial-builds](https://github.com/nodejs/unofficial-builds/issues/197) and will probably also affect https://github.com/nodejs/docker-node. As it turned out, the https://github.com/nodejs/docker-node repo (this one)...

@ziad404 Are you intending to improve this PR or have you dropped it now?

@ziad404 > Just want to make sure that I got your comment , the only section which should be edited is the chaining part , right ? As I wrote...

@ziad404 Check the instructions in https://github.com/cypress-io/cypress-documentation/blob/main/README.md about how to build and view your changes locally before pushing them to GitHub to avoid also build failures in CircleCI.

@AtofStryker Thanks for adding this task and for the detail you provided! This is probably a good repo to pilot this change. - Although the repo publishes to the npm...