[3.12] Remove MSI build from security-only branch#148007
Merged
hugovk merged 1 commit intopython:3.12from Apr 2, 2026
Merged
Conversation
hugovk
changed the title
|
Thanks @hugovk for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11. |
|
Sorry, @hugovk, I could not cleanly backport this to |
|
GH-148008 is a backport of this pull request to the 3.11 branch. |
hugovk
added a commit
that referenced
this pull request
Apr 2, 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
1 participant
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.
We had a recent failure building MSI in the 3.10 branch because Sphinx failed to run.
Rather than try and fix it, we don't need to build installers for security-only branches (currently 3.10-3.12), so let's remove the MSI build to save some CI resources.