Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release/6.0-staging][android] Bump to win 11 helix queue #107450

Merged
merged 1 commit into from
Sep 8, 2024

Conversation

akoeplinger
Copy link
Member

@akoeplinger akoeplinger commented Sep 6, 2024

Backport of #96139 to release/6.0-staging.

Same as #96634 just for the 6.0 branch. Dnceng would like to remove this old Helix queue.

Customer Impact

None, this is an infrastructure change

Testing

CI testing.

Risk

None.

IMPORTANT: If this backport is for a servicing release, please verify that:

  • The PR target branch is release/X.0-staging, not release/X.0.

  • If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Sep 6, 2024
@akoeplinger
Copy link
Member Author

@carlossanlop infra-only change, marking as servicing-approved.

@akoeplinger akoeplinger added Servicing-approved Approved for servicing release area-Infrastructure-mono and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Sep 6, 2024
Copy link
Contributor

Tagging subscribers to this area: @directhex, @matouskozak
See info in area-owners.md if you want to be subscribed.

@steveisok steveisok self-requested a review September 6, 2024 13:04
@akoeplinger
Copy link
Member Author

/ba-g failures are not related to Android so the changes can't have affected them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants