Repository navigation
ci: v2.0 release PR titles without the branch scope - #87
Merged
Merged
Conversation
The conventional-commits check refuses the scope (v2.0) because of its dot,
which led to hand-renamed release PRs and, once, a malformed tag. Title v2.0
release PRs chore: release${component} ${version}, as copick-mcp does.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
uermel
pushed a commit
that referenced
this pull request
Oct 16, 2026
🤖 I have created a release *beep* *boop* --- ## [2.0.0-alpha.4](copick-shared-ui-v2.0.0-alpha.3...copick-shared-ui-v2.0.0-alpha.4) (2026-10-16) ### 🐞 Bug Fixes * compact Edit Object Types dialog with a larger table (v2.0) ([#79](#79)) ([2d56650](2d56650)) ### ⚙ Continuous Integration * v2.0 release PR titles without the branch scope ([#87](#87)) ([a6c4d7c](a6c4d7c)) --- Merging this PR will publish a copick-shared-ui alpha prerelease to PyPI. Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.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.
Release PRs on
v2.0are titledchore(v2.0): release <name> <version>, and the org's conventional-commits check (chanzuckerberg/github-actionsconventional-commits) refuses them: its scope pattern is[a-z][a-z0-9-]*, which has no.. Renaming the PR by hand to get past the check broke a release: copick's 2.0.0-alpha.4 PR was renamed with a trailing space, release-please parsed the version as"2.0.0-alpha.4 ", and GitHub refused the tag.This sets the v2.0 release PR title to
chore: release${component} ${version}(e.g.chore: release copick 2.0.0-alpha.5), the pattern copick-mcp's v2.0 line already uses. release-please writes and parses titles with the same pattern, so releases keep working, and the title passes the check without edits. Checked with release-please 17.6.0 (the action's version): the title formats, parses back to the same component and version, and matches the check's regex.mainis unchanged:chore(main): …already passes.After this merges, release-please retitles any open v2.0 release PR on its next run. Do not rename release PRs by hand: release-please reads the version back from the title.
🤖 Generated with Claude Code