Release tooling: TabPFN-pattern pipeline + Towncrier#278
Open
adrian-prior wants to merge 3 commits intomainfrom
Open
Release tooling: TabPFN-pattern pipeline + Towncrier#278adrian-prior wants to merge 3 commits intomainfrom
adrian-prior wants to merge 3 commits intomainfrom
Conversation
adrian-prior
requested review from
klemens-floege
and removed request for
a team
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
Contributor
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
adrian-prior
requested review from
bejaeger
and removed request for
bejaeger and
klemens-floege
Ports TabPFN's complete release stack to tabpfn-extensions: - release-create-pr.yml: workflow_dispatch -> opens release/v* PR with version bump and Towncrier-assembled CHANGELOG. - release-tag-on-merge.yml: merge of release/v* -> auto-tags merge commit, triggering release-publish.yml. - release-publish.yml: tag push -> build, TestPyPI publish + install verify, gated PyPI publish (manual approval at `pypi` env), auto GitHub Release with notes extracted from CHANGELOG. - check-changelog.yml: enforces every PR adds a changelog fragment via scientific-python/action-towncrier-changelog. - pull_request.yml: adds a build_verify job that runs `uv build` and `twine check` so packaging regressions fail PR CI. - pyproject.toml: adds [tool.towncrier] with 5 categories matching TabPFN (breaking, added, changed, fixed, deprecated). - CHANGELOG.md: drops the empty Added/Changed subsections under [Unreleased] (Towncrier inserts the new release section directly after the Unreleased heading at release time). - changelog/README.md: contributor docs for the per-PR fragment convention. Trusted Publishing replaces all API tokens. No secrets are required for publish steps. The tag-on-merge step uses RELEASE_BOT_TOKEN (a fine scoped PAT) because the default GITHUB_TOKEN can't push tags that trigger another workflow.
adrian-prior
force-pushed
the
release-tooling
branch
from
56076da to
62bc16d
Compare
adrian-prior
changed the title
Bootstrap step: this PR adds check-changelog.yml, which now demands a fragment for every PR including this one.
scientific-python/action-towncrier-changelog requires this marker section in pyproject.toml to know the project opts into the check. Without it the action fails with 'Missing [tool.changelog-bot.towncrier_changelog] section.' Matches TabPFN's setup.
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
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.
Summary
Ports TabPFN's complete release stack — four workflows + Towncrier — to
tabpfn-extensions. After this lands, the release flow becomes: maintainer clicks Run workflow onCreate Release PR, types a version, and the rest is automated through to PyPI and a GitHub Release. PyPI publish is gated by manual approval at thepypienvironment.This supersedes the earlier draft of this PR (which had a smaller, two-file release-publish setup).
Files
.github/workflows/release-create-pr.ymlworkflow_dispatch→ opensrelease/v*PR with version bump and Towncrier-assembled CHANGELOG.github/workflows/release-tag-on-merge.ymlrelease/v*PR → auto-tags the merge commit.github/workflows/release-publish.yml.github/workflows/check-changelog.ymlchangelog/<pr#>.<category>.mdfragment.github/workflows/pull_request.ymlbuild_verifyjob (uv build+twine check)pyproject.toml[tool.towncrier]with 5 categories: breaking, added, changed, fixed, deprecatedCHANGELOG.mdAdded/Changedsubsections under[Unreleased](Towncrier inserts release sections directly after the heading)changelog/README.mdFuture release flow