Skip to content

chore(main): release 0.2.1#13

Closed
github-actions[bot] wants to merge 1 commit intomainfrom
release-please--branches--main
Closed

chore(main): release 0.2.1#13
github-actions[bot] wants to merge 1 commit intomainfrom
release-please--branches--main

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.2.1 (2026-02-16)

Bug Fixes

  • replace broken release-please PR comment with docs (#12) (817b37d)

This PR was generated with Release Please. See documentation.

@github-actions
Copy link
Copy Markdown
Contributor Author

Important

CI checks don't trigger automatically on release-please PRs (created with GITHUB_TOKEN).
Please close and reopen this PR to start CI.

@zeitlinger
Copy link
Copy Markdown
Member

Closing: the only change (817b37d) was a docs/CI fix incorrectly prefixed with fix:. No functional change warrants a release. A future release-please PR will include this commit if needed.

@zeitlinger zeitlinger closed this Feb 16, 2026
zeitlinger added a commit that referenced this pull request Feb 16, 2026
## Summary

- Closed PR #13 (unnecessary v0.2.1 release triggered by `fix:` prefix
on a docs-only change)
- Added release impact note to CLAUDE.md commit message conventions,
explaining that only `feat` and `fix` types trigger releases

## Context

Commit 817b37d used `fix:` for a docs/CI change, which caused
release-please to open an unnecessary release PR. This adds guidance to
prevent that in the future.

## Test plan

- [x] `mise run fix` passes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant