Repository navigation
Update Branch Protection Rules for release branches post Python 3.9 removal #179
Description
The Branch Protection rules for our release branches have been updates.
Old:
- The existing branch protection rules for the Release branches were set to "release/*", which doesn't apply any longer.
New:
-
[NOT DONE] Create a branch release protection rules for future release branches (0.5, etc). This can't be done until the 0.5.0 branch is created. This fnmatch will look like:
-
[NOT DONE] Update the "main" branch protection rule to require Python 3.12, 3.13, and 3.14. This required Add support for Python versions 3.12, 3.13, and 3.14 #177 to be merged into main.
-
[Done] Update the Branch Protection Rules for branches 0.1,0.2,0.3,0.4 to require Python 3.9 / 3.10 / 3.11. Note the revised fnmatch
syntax uses globbing patterns, not regex — similar to shell wildcards (This is what GitHub uses).
This makes the ruleset only apply to our 3.9 release branches:
Activity
cleemullins commentedon Oct 20, 2025
The main branch protection rule has been updated to require newer vesions of Python - aligning with our build matrix.
cleemullins commentedon Oct 20, 2025
Branch protection rules are updated, using the new GitHub Rulesets. As part of this I relaxed the actual branch protection rules on main to simply "Require a PR". All the meaningful rules are moved to the rulesets, as this seems the right long-term answer.
Rulesets have been created for:
The 0.1 - 0.4 rules is requiring Python 3.9 / 3.10 / 3.11 builds to pass.
The 0.5 - 0.9 rule is requiring Pythin 3.10 / 11 / 12 / 13 / 14 to pass.