Repository navigation
Predictable updates of yarn version #388
Description
Activity
See also #386 (comment)
Reacted by Peter PetrovYarn will continued to be updated when Node.js version are updated. However, since Yarn is still experimental and has not reached a stable version (eg. 1.0) there may be breaking changes. Use on own risk.
If this is really the stance being taken, then I believe that there should be a separate tag for the builds that include yarn. Having the image change every time yarn decides to do a release breaks the concept of fixed/reproducible builds in Docker.
Reacted by Franz Josef KaiserThink this is answered in the CONTRIBUTING.md now
Yarn is updated to the latest version only when there is a new Node.js SemVer-minor release, and it's updated only in the branch with the new release, preferably in the same PR. The update.sh script does this automatically when invoked with a specific branch, e.g. ./update.sh 6.10.
When the yarn version changes, it means that a new base image is generated. Can this be limited to a predictable schedule? I was thinking that update to the latest stable version of yarn when a new point release is made.