[6.0] Missing version number bump#86600
Merged
carlossanlop merged 1 commit intodotnet:release/6.0-stagingfrom May 22, 2023
carlossanlop:MissingVersionBump6
Merged
[6.0] Missing version number bump#86600carlossanlop merged 1 commit intodotnet:release/6.0-stagingfrom carlossanlop:MissingVersionBump6
carlossanlop merged 1 commit intodotnet:release/6.0-stagingfrom
carlossanlop:MissingVersionBump6
Conversation
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsMissed a version number bump in the original PR: #86298 cc @elinor-fung @vitek-karas sorry for the noise.
|
ViktorHofer
approved these changes
May 22, 2023
Contributor
Author
|
All failures are known and I'm not seeing the HostActivation failure anymore. Merging now. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Missed a version number bump in the original PR: #86298
There is already a 6.0 issue open that preexisted the above PR, but it's unrelated. Some of those failures will go away after merging this, but the issue should stay open.
cc @elinor-fung @vitek-karas sorry for the noise.