-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
[3.11] gh-123418: Update CI to use fresh OpenSSL releases (GH-123675) #123699
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…onGH-123675) Also adds openssl/openssl GitHub URL template for newer OpenSSL downloads (cherry picked from commit 56b00f4) Co-authored-by: Zachary Ware <[email protected]>
e67d55a
to
cf5a533
Compare
Figured out that the issue was that the cached OpenSSLs were built on a newer OS. This now changes the cache key to include the OS version by using The other option is to update these jobs to |
Good find!
We could use something like what we do in cpython/.github/workflows/build.yml Lines 58 to 63 in ef530ce
This evaluates to
https://github.com/python/cpython/actions/runs/10877514251/job/30179004543#step:5:4 So a And let's forward-port these key changes to 3.12-3.14 as well.
It's worth doing this as well, Ubuntu 20.04 is EOL next April and at some point GitHub will stop updating |
GH-124403 is the forward-port. I opted not to add |
Also adds openssl/openssl GitHub URL template for newer OpenSSL downloads
(cherry picked from commit 56b00f4)