tools: pin OpenSSL to 3.5.4 on test-shared workflow#60428
Merged
nodejs-github-bot merged 2 commits intonodejs:mainfrom Oct 30, 2025
Merged
tools: pin OpenSSL to 3.5.4 on test-shared workflow#60428nodejs-github-bot merged 2 commits intonodejs:mainfrom
nodejs-github-bot merged 2 commits intonodejs:mainfrom
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Because of #60088, we cannot yet test with OpenSSL 3.6.0. Pinning to unblock #60315.
Also adding
cachix/cachix-actionso we don't need to build OpenSSL every time. PRs from forks won't have access to the secret, but that's on purpose, so they can benefit from the read-only cache, but cannot do any cache poisoning.