Repository navigation
ci: v2.0 release PR titles without the branch scope - #129
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>
…k repos do v1.5.0 accepts only chore, feat, fix, revert, docs and style, and scopes of lowercase letters and spaces, so it refused ci/test/perf/build titles. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
uermel
added a commit
that referenced
this pull request
Oct 16, 2026
chimerax-copick runs the conventional-commits check at v1.5.0, which accepts only `chore`, `feat`, `fix`, `revert`, `docs` and `style` and scopes of lowercase letters and spaces. It refuses `ci:`, `test:`, `perf:`, `build:` and `deps:` titles that every other copick repo (v6.x) accepts. This runs it at v6.41.3, as copick and copick-easymode do. The v2.0 line gets the same bump in #129. 🤖 Generated with [Claude Code](https://claude.com/claude-code) 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.7](chimerax-copick-v2.0.0-alpha.6...chimerax-copick-v2.0.0-alpha.7) (2026-10-16) ### ✨ Features * colour filaments by object, and filament transparency (v2.0) ([#126](#126)) ([2d7821f](2d7821f)) ### 🐞 Bug Fixes * duplicate filament sets, meshes and segmentations (v2.0) ([#124](#124)) ([c323172](c323172)) * require copick-shared-ui 2.0.0a4 ([#132](#132)) ([e358c24](e358c24)) ### ⚙ Continuous Integration * v2.0 release PR titles without the branch scope ([#129](#129)) ([644c279](644c279)) --- Merging this PR will publish a chimerax-copick alpha GitHub prerelease. It will not publish to the ChimeraX Toolshed. 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.
chimerax-copick only: the conventional-commits check also moves from v1.5.0 to v6.41.3 (as copick uses). v1.5.0 refused
ci:and other types, and any scope with a digit (#130 does the same onmain).🤖 Generated with Claude Code