ansible: upgrade to OpenSSL 1.1.0i & 1.0.2p in sharedlibs #1451
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
OpenSSL 1.1.1-pre8 too
rvagg
force-pushed
the
rvagg/docker-sharedlibs-openssl-upgrade
branch
from
32d9336
to
d2cd05b
Compare
|
pulled in OpenSSL 1.1.1-pre8 too, we're getting close to 1.1.1 final so it's time to start getting serious I reckon |
2 tasks
|
So this makes for an interesting situation. ATM nothing in our repo passes CI (e.g. v10.8, or master).
/CC @Trott @joyeecheung @nodejs/testing |
|
Since nodejs/node#22318 is going out in a release Real Soon Now, any reason not to fast-track it and land it on master? It's already landed on |
|
FTR the expected failures are:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
running upgrades now, it'll require restart of those containers but since CI is locked down that should be easy