Skip to content

chore(main): release 0.5.1 - #14

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

chore(main): release 0.5.1#14
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown

🤖 I have created a release beep boop

0.5.1 (2026-09-03)

Bug Fixes

  • add conventional-commit prefix to dependabot PR titles (#11) (3aaa1e5)
  • seed release-please's version baseline correctly (#13) (8b4982a)

This PR was generated with Release Please. See documentation.

@dconlan

dconlan commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Closing - this was generated before #15/#16 merged, and its standing branch has a stale CHANGELOG.md that drops the just-merged backfilled history instead of building on it. Closing so release-please regenerates fresh against current main.

@dconlan dconlan closed this Sep 3, 2026
dconlan added a commit that referenced this pull request Sep 3, 2026
Baic -> Basic, editted -> edited, setings -> settings, Unfortunetly ->
Unfortunately, availble -> available.

Also serves as a deliberate, real trigger to verify release-please
correctly merges its new entry with the just-backfilled CHANGELOG.md on
main, rather than treating it as a new/empty file again (as it did for
the now-closed #14) — this repo has never had a release-please PR
actually merged, so this is genuinely untested territory.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
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