Update resourceManagement for 10.0.8 milestone#66432
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the repo’s GitHub resource management policy to assign the new servicing milestone for PRs merged into the release/10.0 branch, aligning automation with the newly created 10.0.8 milestone after 10.0.7 was released.
Changes:
- Update milestone assignment for
release/10.0PR closures from10.0.7to10.0.8.
Member
|
based on #65976, we probably should bump net9 and net8 versions? |
DeagleGross
approved these changes
Apr 23, 2026
Member
Author
|
@wtgodbe Please take a look. Also please double check if the milestone for the following PRs need to be updated to 10.0.8 |
wtgodbe
approved these changes
Apr 23, 2026
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
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.
10.0.7 is already released. I created a new milestone for 10.0.8, closed the 10.0.7 milestone, and updating resourceManagement to start adding 10.0.8 milestone.
We might have been adding 10.0.7 milestone for few recent PRs incorrectly.