Repository navigation
ci: release with changie and changie-release-action v2 - #26
Merged
Merged
Conversation
Replace bumpversion with changie. A release job in the test workflow maintains a release PR and, once merged, tags the version and creates the GitHub release with the release app token. That triggers the existing python-release.yml, which keeps publishing to PyPI with trusted publishing. Older history stays in CHANGES; CHANGELOG.md starts at 0.1.0.
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.
Switch releases to changie and
labd/changie-release-actionv2.0.0..changie.yaml(kinds incl. Dependency/Security → patch) withreplacementsfor every hardcoded version:pyproject.toml,src/django_session_timeout/__init__.py,docs/conf.py..bumpversion.cfgis removed.releasejob in the test workflow (push to the default branch only, after all checks): maintains achangie-release/<branch>release PR; once merged it tags the version and creates the GitHub release (create-release: true) with the release app token.uv lockruns asversion-command.python-release.yml(release: created), which still publishes to PyPI with trusted publishing. Nothing changes on pypi.org.dependabot-changie.yamladds a Dependency entry to Dependabot PRs.CHANGELOG.mdstarts at the current release (0.1.0, tag0.1.0, on PyPI); older history stays inCHANGES. Tags keep the existingX.Y.Zformat (changie keeps the prefix-less format).Removedentry for the unreleased Python 3.11+ / Django 5.2+ change, so after merge a release PR for 1.0.0 opens. Change the entry kind if you prefer another version.Verified locally:
changie batch auto --dry-run→ 1.0.0; a simulated bump updates all version strings,uv lock --checkpasses afteruv lock; ruff and tests pass.