fix(skill): re-trigger release-please after #44 parse error#45
Merged
Conversation
The squash-merge commit for #44 included a multi-line code fragment with unbalanced braces across a wrapped line, which made the conventional-commits parser bail on the entire commit. release-please then saw zero parseable commits since v1.6.0 and skipped opening a release PR. This empty commit re-triggers the workflow with a clean body so 1.6.1 can ship.
lxcong
changed the title
lxcong
added a commit
that referenced
this pull request
May 14, 2026
🤖 I have created a release *beep* *boop* --- ## [1.6.1](v1.6.0...v1.6.1) (2026-05-14) ### Bug Fixes * **skill:** re-trigger release-please after [#44](#44) parse error ([#45](#45)) ([3caa5c3](3caa5c3)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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.
Why
PR #44 merged successfully (the SKILL.md telemetry fix is on
main),but release-please did not open a 1.6.1 release PR.
Looking at the workflow log of the post-merge run, the conventional-commits
parser bailed on the squash-merge commit:
GitHub's squash-merge took the full PR body (which contained inline code
fragments with
{}and()) and wrapped one of them across a lineboundary. That left an unbalanced expression that the parser treats as a
hard error, dropping the whole commit from the release window.
Result: release-please saw zero parseable commits since v1.6.0 and
skipped opening a release PR.
Fix
A single empty commit with a clean body so release-please re-runs with a
parseable commit chain. Code on
mainis unchanged; the diff is zerofiles / zero lines.
Test plan
braces — should parse cleanly.
chore(main): release 1.6.1PR that includes the SKILL.md fix from fix(skill): align telemetry dispatch and field name with server #44.🤖 Generated with Claude Code