Add Jammy stack to .NET 6 dependencies #365
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
ForestEckhardt
previously approved these changes
Jul 7, 2022
This was referenced Jul 8, 2022
|
I've updated the dep-server's known versions file for this dependency; the dep server's metadata should be updated shortly. |
ForestEckhardt
previously approved these changes
Jul 13, 2022
ForestEckhardt
approved these changes
Jul 13, 2022
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.
Summary
The Paketo Jammy Stacks RFC has been accepted, and specifies that the Jammy Full and Base stacks will have the stack ID
io.buildpacks.stacks.jammy. .NET 3.1 does not work on Jammy Jellyfish because it requires an outdated version of OpenSSL. So, this PR adds the Jammy stack only to the .NET 6 dependencies.A related dep-server PR will honor this change for new versions of .NET as they're added. Once this is approved, I'll also updated the existing
metadata.jsonfor the dependencies currently in the buildpack to reflect this change.Use Cases
Will allow the .NET Core buildpack to run on Jammy.
Checklist