install libssl 1.1 to support older .NET SDKs #11741
Merged
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
sebasgomez238
approved these changes
Mar 5, 2025
jeffwidman
approved these changes
Mar 6, 2025
randhircs
force-pushed
the
dev/brettfo/nuget-libssl
branch
from
0b2b5db to
f8593ff
Compare
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.
The NuGet updater installs SDKs as specified in a repo's
global.jsonfiles then wherever possible, uses that version of the SDK for various update operations. Older versions of the .NET SDK (e.g., 3.1.xxx) require libssl 1.1, but that's not available on the current updater image nor on the install sources so it needs to be manually installed.Found during a manual internal log audit.