Repository navigation
ci: release with changie and changie-release-action v2 - #27
Merged
Merged
Conversation
Replace the manual prepare-release workflow with a release job in the test workflow. It maintains a release PR and, once merged, tags the version and creates the GitHub release with the release app token. python-release.yml (the PyPI trusted publisher) now runs on that release instead of on CHANGELOG.md pushes: it builds, publishes to PyPI, attaches the dist files and SBOMs to the release and uploads the SBOM to DependencyTrack, as before.
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
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.
Move the existing changie setup to
labd/changie-release-actionv2.0.0.releasejob intest.yml(push tomasteronly, after the tests): maintains achangie-release/masterrelease PR; once merged it tags the version and creates the GitHub release (create-release: true) with the release app token.uv lockruns asversion-command. Replaces the manualprepare-release.yml.python-release.yml(the PyPI trusted publisher, environmentpypi) now runs onrelease: createdinstead of on pushes that touchCHANGELOG.md. It checks the tag matches the package version, builds, publishes to PyPI, uploads the dist files and SBOMs to the release and sends the SBOM to DependencyTrack as before. Workflow file and environment are unchanged, so nothing changes on pypi.org..changie.yaml: adds theDependencykind (patch); the existingreplacementsalready coverpyproject.tomland theVERSIONtuple in__init__.py.dependabot-changie.yamladds a Dependency entry to Dependabot PRs.X.Y.Zformat.Verified locally:
changie batch auto --dry-run→ 3.0.0 (from the pendingremovedfragment); a simulated bump updatespyproject.toml,__init__.pyanduv.lock,uv lock --checkpasses; ruff and tests pass.