ci: adopt release-please for automated releases - #448
Merged
Conversation
Replace the manual scripts/release.sh + github-changelog-generator flow with release-please: - release-please-config.json / .release-please-manifest.json drive a Python release that bumps pyproject.toml and prepends CHANGELOG.md from the Conventional Commits since the last tag. - release.yml maintains a release pull request on every push to master; merging it creates the vX.Y.Z tag and GitHub release, then builds and publishes to PyPI via OIDC trusted publishing (no token secret). - build.yml is trimmed to tests only; the publish job and the tag trigger move to release.yml. - pyproject.toml drops the aN development version, since release-please now owns version bumps. Release-As: 2.13.0
pdecat
added a commit
that referenced
this pull request
Jul 18, 2026
The manual scripts/release.sh + github-changelog-generator flow was replaced by release-please (#448); point the Development "release" step and the Changelog note at it.
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.
Replaces the manual
scripts/release.sh+ github-changelog-generator flow with release-please.How it works now
master, release-please maintains a release PR that bumpspyproject.tomland prependsCHANGELOG.mdfrom the Conventional Commits since the last tag.vX.Y.Ztag + GitHub release, and thepublishjob builds and uploads the distributions to PyPI.release.ymland thereleaseenvironment.build.ymlis now tests-only; the publish job and the tag trigger moved torelease.yml.pyproject.tomldrops theaNdev-version dance since release-please owns version bumps.Before the first release (one-time PyPI setup)
Add a Trusted Publisher on the PyPI
aws-adfsproject (Manage -> Publishing) with:venthaws-adfsrelease.ymlreleaseOnce that's in place the OIDC publish works with no secrets. The old
pypi_password/test_pypi_passwordrepo secrets can be dropped afterwards.This release (2.13.0)
The Duo Universal Prompt PR (#447) was squash-merged with a non-Conventional subject, so release-please can't infer it. This commit carries a
Release-As: 2.13.0footer so the first release PR targets 2.13.0. Worth a quick curate of that PR's changelog to headline the Duo feature (link #447) before merging; everything after this is automatic from Conventional Commit subjects.