Add patch-release JSON files #9480
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
|
We should decide what we want to do w/schemas for these new files. Context: #9431 (comment) |
Falco20019
approved these changes
Aug 23, 2024
leecow
approved these changes
Aug 30, 2024
|
Please stop posting these messages @admin-xspace. |
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.
I generated patch-release files for 8.0+. That was a choice. We can make a different choice.
There are links to blob storage. We can copy the files before merging or we make these GH links (it's just a code change) while we're getting this all figured out. Either works for me.
https://github.com/dotnet/core/pull/9480/files#diff-4792c8566cd38c9a12d0f0d06b0c9fc272aa7c941324a18da65dc9223b05955bR11
Contributes to #9417 and borrows from #9427.
@Falco20019 @leecow