Skip to content

ci: run the conventional-commits check at v6.41.3 - #130

Merged
uermel merged 1 commit into
mainfrom
uermel/conventional-commits-v6
Oct 16, 2026
Merged

uermel merged 1 commit into
mainfrom
uermel/conventional-commits-v6

Conversation

@uermel

@uermel uermel commented Oct 16, 2026

Copy link
Copy Markdown
Member

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

…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
uermel merged commit b1567a2 into main Oct 16, 2026
1 check passed
uermel added a commit that referenced this pull request Oct 16, 2026
Release PRs on `v2.0` are titled `chore(v2.0): release <name>
<version>`, and the org's conventional-commits check
(`chanzuckerberg/github-actions` `conventional-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. `main` is 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 on `main`).

🤖 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*
---


##
[1.16.0](chimerax-copick-v1.15.1...chimerax-copick-v1.16.0)
(2026-10-16)


### ✨ Features

* colour filaments by object, and filament transparency
([#125](#125))
([f401453](f401453))


### 🐞 Bug Fixes

* duplicate filament sets, meshes and segmentations
([#123](#123))
([320871d](320871d))
* require copick-shared-ui 0.8.1
([#131](#131))
([cc4ef81](cc4ef81))


### ⚙ Continuous Integration

* run the conventional-commits check at v6.41.3
([#130](#130))
([b1567a2](b1567a2))

---
Merging this PR will release ChimeraX-Copick on GitHub.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant