Skip to content

ci: support releases from v* branches - #1178

Merged
henryiii merged 1 commit into
pypa:mainfrom
henryiii:release-branches
Sep 5, 2026
Merged

ci: support releases from v* branches#1178
henryiii merged 1 commit into
pypa:mainfrom
henryiii:release-branches

Conversation

@henryiii

@henryiii henryiii commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

🤖 AI text below 🤖

The pre-release workflow, the local release script, and the test workflow only accepted main. This lets them also run on v* maintenance branches:

  • pre-release.yml: run on main or v*, check out the dispatched ref, push back to the dispatched branch.
  • tasks/release.py: push to the current branch instead of main.
  • test.yml and cd.yml: trigger on pushes and PRs for v* branches.

The release and pypi GitHub environments need v* added to their branch rules before a release from a v1 branch can run.

Assisted-by: ClaudeCode:claude-fable-5-1
@henryiii
henryiii merged commit 1186a34 into pypa:main Sep 5, 2026
60 checks passed
@henryiii
henryiii deleted the release-branches branch September 5, 2026 20:28
henryiii added a commit that referenced this pull request Sep 9, 2026
🤖 _AI text below_ 🤖

The pre-release workflow, the local release script, and the test
workflow only accepted `main`. This lets them also run on `v*`
maintenance branches:

- `pre-release.yml`: run on `main` or `v*`, check out the dispatched
ref, push back to the dispatched branch.
- `tasks/release.py`: push to the current branch instead of `main`.
- `test.yml` and `cd.yml`: trigger on pushes and PRs for `v*` branches.

The `release` and `pypi` GitHub environments need `v*` added to their
branch rules before a release from a `v1` branch can run.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants