Skip to content

馃懛 ci: publish GitHub Release after PyPI - #280

Merged
gaborbernat merged 1 commit into
pytest-dev:mainfrom
gaborbernat:github-release-after-pypi
Oct 18, 2026
Merged

gaborbernat merged 1 commit into
pytest-dev:mainfrom
gaborbernat:github-release-after-pypi

Conversation

@gaborbernat

@gaborbernat gaborbernat commented Oct 18, 2026 •

Copy link
Copy Markdown
Collaborator

PyPI publication can finish without a matching GitHub Release, leaving the published changelog and version diff hard to find from GitHub.

A separate job now creates the GitHub Release after PyPI succeeds. It uses the tagged changelog section, links the PyPI version and previous tag comparison, and holds GitHub write access only in that job. The release and preparation workflows pin the current uv and App-token actions.

All 25 existing GitHub Release bodies now use the same format. Four older PyPI versions have no repository tag and remain unresolved. The repository-only App remains responsible for protected release commits and tags. This internal workflow change uses skip news.

@gaborbernat gaborbernat added the skip news PR does not need a changelog entry label Oct 18, 2026
@gaborbernat
gaborbernat merged commit 6e4ac64 into pytest-dev:main Oct 18, 2026
13 of 23 checks passed
@gaborbernat
gaborbernat deleted the github-release-after-pypi branch October 18, 2026 20:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip news PR does not need a changelog entry

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant