Conversation
bboe
force-pushed
the
ci-setup
branch
3 times, most recently
from
8d7f8ee to
0f380f1
Compare
CI:
- ci.yml: add workflow_dispatch trigger and Python 3.14 to the test matrix
- pyproject.toml: add py314 tox env and the 3.14 classifier
Release pipeline (reuses the shared praw-dev/.github workflows, like
praw/prawcore):
- CHANGES.rst: adopt praw's changelog format (semantic-versioning intro line)
- prepare_release.yml: call the reusable prepare_release workflow with
package=codesorter, version_file=const.py, passing the org App secrets
- tag_release.yml: call the reusable tag_release workflow (v1.4.0, which
derives the prepare_release owner from github.repository_owner)
- remove the bespoke tools/{set_version,bump_version,extract_changelog}.py
scripts and their now-dead ruff ignores
Drop the transitional `master` branch trigger from ci.yml, scorecard.yml, and
tag_release.yml now that the default branch is `main`.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
Sets up CodeSorter's CI/release pipeline, reusing praw-dev's shared release tooling.
CI
ci.yml— addworkflow_dispatchtrigger and Python 3.14 to the test matrix.pyproject.toml— addpy314totox.envlistand the3.14classifier.Release pipeline
CHANGES.rst— adopt praw's changelog format (codesorter follows semantic versioning …) sopraw-releaseoperates on it unchanged.prepare_release.yml— bump version + changelog viapraw-release bumpinstead of the bespoketools/set_version.py. Kept self-contained (the reusableprepare_releaseneeds a praw-dev org App secret CodeSorter doesn't have).tag_release.yml(new) — a thin wrapper calling the shared reusable workflowpraw-dev/.github/.github/workflows/tag_release.yml@v1.4.0. That workflow was generalized (Derive prepare_release owner from github.repository_owner in tag_release .github#19) to derive theprepare_releaseowner fromgithub.repository_owner, so it now works for any org while staying identical for praw/prawcore.tools/{set_version,bump_version,extract_changelog}.pyand their deadtools/*.pyruff ignores.Branch rename
mastertrigger fromci.yml,scorecard.yml, andtag_release.ymlnow that the default branch ismain.Verification
praw-releasecycle (bump → unreleased → extract-version → changes) against the converted changelog locally.Notes
tag_releaserequires release PRs to be merged with a merge commit (not squash), same assumption as praw/prawcore.v1.4.0(9ff8957).🤖 Generated with Claude Code