[Mono.Android] Bind API-37.1 - #12388
Open
jonpryor wants to merge 2 commits into
Open
Conversation
jonpryor
requested review from
jonathanpeppers and
simonrozsival
as code owners
August 14, 2026 14:01
jonpryor
force-pushed
the
dev/jonpryor/jonp-bind-api-37.1
branch
2 times, most recently
from
August 14, 2026 16:16
0c4f996 to
ec888bb
Compare
Context: https://developer.android.com/about/versions/17/qpr2 Android 17 QPR2 has been released. * [API-37.1 vs. API-37][0] We completely missed "c-2" Beta 1 and Beta 2; it's now final! (Why "c-2"? Presumably because ["c" was CinnamonBun][1], and Android 17 QPR2 is the second "c" release…) @jonpryor cannot even find an *announcement* for QPR2! Step 1: bind it! Step 2: Enumify it, make stable. This is Step 1. We consider this binding *unstable* until we complete enumification (Step 2). [0]: https://developer.android.com/sdk/api_diff/37.1/changes [1]: https://discord.com/channels/732297728826277939/732297837953679412/1537836773986533506
jonpryor
force-pushed
the
dev/jonpryor/jonp-bind-api-37.1
branch
from
August 14, 2026 16:57
ec888bb to
4ca2a65
Compare
PackDotNet runs after BuildDotNet and the workload smoke test, which can leave SDK tool assemblies loaded by MSBuild. Reuse the existing project-reference outputs when building additional API levels instead of attempting to overwrite those loaded assemblies. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: d4a928f6-8b81-4458-adaf-1e5ca954cd68
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
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.
Context: https://developer.android.com/about/versions/17/qpr2
Android 17 QPR2 has been released.
We completely missed "c-2" Beta 1 and Beta 2; it's now final!
(Why "c-2"? No idea, but that's what the URL for
c-2-beta1 contains. Maybe "CANARY-2"?)
@jonpryor cannot even find an announcement for QPR2!
Step 1: bind it!
Step 2: Enumify it, make stable.
This is Step 1. We consider this binding unstable until we complete enumification (Step 2).
Pull Request
title and
description
should follow the
commit-messages.mdworkflow documentation, and in particular should include: