Skip to content

Revert "[ci] Apply dotnet/maui Android 37 patch (#11302)"#11309

Merged
simonrozsival merged 1 commit intomainfrom
jonathanpeppers/revert-api-37-workaround
May 8, 2026
Merged

Revert "[ci] Apply dotnet/maui Android 37 patch (#11302)"#11309
simonrozsival merged 1 commit intomainfrom
jonathanpeppers/revert-api-37-workaround

Conversation

@jonathanpeppers
Copy link
Copy Markdown
Member

This reverts commit 1b0756f.

dotnet/maui net11.0 now has API 37 in it, so the CI workaround patch is no longer needed.

Copilot AI review requested due to automatic review settings May 8, 2026 15:38
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Removes a temporary CI patch that forced dotnet/maui net11.0 to use Android API 37, based on the premise that MAUI now carries the required API 37 updates and the workaround is no longer needed.

Changes:

  • Deletes the MAUI patch file that updated Android target framework/API defaults to 37.
  • Removes the Azure Pipelines step that applied that patch to the checked-out dotnet/maui repo during MAUI integration testing.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
build-tools/automation/maui/android37-target-framework.diff Removes the no-longer-needed patch content used to bump MAUI to Android API/TFM 37.
build-tools/automation/azure-pipelines.yaml Removes the pipeline step that applied the deleted patch to the MAUI checkout.

@jonathanpeppers
Copy link
Copy Markdown
Member Author

image

@jonathanpeppers jonathanpeppers added the ready-to-review This PR is ready to review/merge, I think any CI failures are just flaky (ignorable). label May 8, 2026
@simonrozsival simonrozsival merged commit c550ad5 into main May 8, 2026
6 of 7 checks passed
@simonrozsival simonrozsival deleted the jonathanpeppers/revert-api-37-workaround branch May 8, 2026 23:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-to-review This PR is ready to review/merge, I think any CI failures are just flaky (ignorable).

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants