Would this mean that you wouldn't need openssl to install volta?

@alvarlagerlof Yes, exactly! That's actually one of the main motivations for this suggested change (see the linked RFC): Dealing with all of the different OpenSSL versions—trying to detect the appropriate one, fetch the correct binary, etc.—is a major pain point in our Linux installer. This would simplify all of that by statically linking to a Rust-based TLS/SSL implementation and avoiding all of the headaches that come with dynamically-linked OpenSSL.

@charlespierce I guess this PR would also allow #1049 to move forward, right?
I'm using volta on an EC2 with the Graviton2 ARM CPU and at the moment have to compile it myself, but would much prefer volta to release prebuilt binaries.

@ZauberNerd Yes, I believe this would allow that change to move forward as well, since it would remove the OpenSSL issues that ran into. The shift to Scientific Linux CERN 6 may also help alleviate the toolchain issues.

@charlespierce that's awesome! Is there something I could do to help get this PR out of the draft state?

@ZauberNerd I don't think there's anything left on this PR directly (other than resolving the merge conflicts). I'm leaving this in draft for now mostly to make sure that we don't accidentally merge it 😄 There's some infrastructure work we'll need to do before merging to make sure we don't break existing installs while we work towards the actual release of this change.

@charlespierce what (if anything) can I do to unblock this over this coming week? Would love to help get it landed!

@chriskrycho I think the only thing remaining is landing this PR (and then some testing when we cut the release). My initial thoughts were being a little wary of version churn with the in-progress pnpm implementation, but I think there's enough significant changes between this and Yarn 3 support, plus there are some follow-ups needed for pnpm, so I'd lean towards getting this merged (along with any smaller outstanding PRs), and then cutting it all as version 1.1.

I'll update this to resolve the merge conflicts and also put out a PR to clean up some additional warnings we seem to be getting.

That seems reasonable to me! Let's do it!

itshappening.gif

Wow this is huge! Thanks to everyone involved who helped to solve those openSSL linking issues with this PR.

Is it possible to get an "official" v1.1.0 release after the merge?

That's precisely the plan—this and Yarn 3 support will be the headliner features! (With, hopefully, a 1.2 with pnpm support landing relatively soon after that. 🤞🏼)