Repository navigation
ci: title v2.0 release PRs so release-please can read them back - #36
Merged
Merged
Conversation
release-please titles a linked (server + client) release PR after the branch,
"chore: release ${branch}". On v2.0 that is "chore: release v2.0", which
release-please later reads back as version "2.0" and fails on ("unable to
parse version string: 2.0"). It has failed on every v2.0 push since #28 was
merged, so #28's 1.0.0-alpha releases were never created and no new release
PR was opened.
Give v2.0 release PRs the title "chore(v2.0): release copick-web": skipped
when release-please looks for earlier releases, parsed when it creates the
release (the versions come from the PR body).
Co-Authored-By: Claude Opus 5.5 <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.
No release PR is opened on
v2.0: "Create Release PRs" has failed on every push since #28 was merged, withrelease-please failed: unable to parse version string: 2.0.Cause. release-please titles a linked (server + client) release PR after its branch,
chore: release ${branch}. Onmainthat giveschore: release main, which release-please later skips when it scans merged PRs for the latest release. Onv2.0it giveschore: release v2.0: the scan's pattern (chore${scope}: release${component} ${version}) readsv2.0as version2.0, and parsing it throws. So #28's1.0.0-alphareleases and tags were never created (it is stillautorelease: pending), and no new release PR was opened.Fix.
group-pull-request-title-pattern: "chore${scope}: release copick-web"in the v2.0 prerelease config, so v2.0 release PRs are titledchore(v2.0): release copick-web. Checked against release-please 17.6.0's own parser: the scan skips that title (no crash), and creating the release parses it with the group pattern (the versions come from the PR body, as onmain). The old title reproduces the error exactly.After merging. #28 has been retitled to
chore(v2.0): release copick-web, so the next run onv2.0should create theserver-v1.0.0-alpha/client-v1.0.0-alphareleases from it (and publish the images), then open a release PR for #32–#34.mainis unaffected: its config has no group title, andchore: release mainalready works.🤖 Generated with Claude Code