Repository navigation
Conversation
The release-pr skill and CONTRIBUTING said a release with no public API change bumps the build number (0.1.2+1), but release_tag's regex stops at the `+` and release_publish's tag filters don't match it, so that release could never be tagged or published. Bump the patch instead, and say why in all three docs. Also ignore .claude/worktrees/ now that .claude/skills is committed. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012vTgFujZpZYefYYqjjD8jy
Member
Author
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
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.
The release-pr skill and CONTRIBUTING said a release with no public API change bumps the build number (
0.1.2+1). The release workflows from #46 can't ship that:release_tag's version regex stops at the+, so the tag comes out asv0.1.2and fails the pubspec check, andrelease_publish's tag filters don't match a+either.1.0.0a no-API-change release now bumps the patch, like a feature release, with the reason stated once in each..gitignore: ignores.claude/worktrees/, which shows up as untracked now that.claude/skills/is committed.Verified by running
release_tag's regex in bash:chore(repo): release v0.1.2+1 (#50)yieldsv0.1.2, whilev0.1.3passes through unchanged.🤖 Generated with Claude Code
https://claude.ai/code/session_012vTgFujZpZYefYYqjjD8jy