[release/10.0.2xx] Fix -extra container variant check to support .NET 9+#52598
Merged
baronfel merged 8 commits intorelease/10.0.2xxfrom Jan 29, 2026
Merged
Conversation
… .NET 9/10 Co-authored-by: baronfel <573979+baronfel@users.noreply.github.com>
Co-authored-by: baronfel <573979+baronfel@users.noreply.github.com>
Co-authored-by: baronfel <573979+baronfel@users.noreply.github.com>
Co-authored-by: mthalman <15789599+mthalman@users.noreply.github.com>
baronfel
added
Servicing-consider
Area-Containers
This was referenced Jan 23, 2026
dsplaisted
approved these changes
Jan 29, 2026
This was referenced Feb 12, 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.
Backport of #52161 to release/10.0.2xx
Fixes #52160
Customer Issue
Users trying to publish non-invariant applications onto our 'chiseled' containers found that the SDK tooling wasn't inferring a container with globalization support, as documented. While users could workaround this by explicitly specifying the base image and/or image family, the UX of correct base image inference is a key selling point of the containerization feature and forcing users to manually specify complete base images runs the risk of those image tags becoming stale.
Was this a regression?
Testing
New tests have been added that verify inference for the boundary conditions.
Risk
Low - this area is under extensive testing now and has a low blast radius.