fix releases index channel 2.2 security #10009
Merged
+1
−1
Conversation
This file contains hidden or 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
victorisr
approved these changes
Aug 1, 2025
danroth27
pushed a commit
that referenced
this pull request
Aug 8, 2025
Co-authored-by: Ondrej Smid <ondrejsmid@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
I found a mismatch between releases-index.json and releases.json for channel 2.2, mismatch in a field "security".
Found during development of https://github.com/dotnet/release/issues/1346 which will be used for synchronizing GitHub releases.json with CDN and this sync process also validates that values in releases-index.json match with values in the latest release in releases.json.
I believe this
securityshould befalseas there is a statement ".NET Core 2.2.8 release carries only non-security fixes." in a linked release notes 2.2.8.md.I know there won't be any updates of channel 2.2 info, but good to have this consistency I hope (otherwise I have to have some special exclusions in the sync tool).