Skip to content

chore(main): release 0.2.0 - #14

Merged
tas50 merged 1 commit into
mainfrom
release-please--branches--main--components--busser-bash
Aug 28, 2026
Merged

tas50 merged 1 commit into
mainfrom
release-please--branches--main--components--busser-bash

Conversation

@kitchen-porter

@kitchen-porter kitchen-porter commented Aug 28, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.2.0 (2026-08-28)

⚠ BREAKING CHANGES

  • Ruby 3.1 and busser releases older than 0.9.0 are no longer supported.

Features

  • require Ruby 3.2 and busser 0.9, adopt release-please (3e7a605)

This PR was generated with Release Please. See documentation.

@kitchen-porter kitchen-porter changed the title chore(main): release 1.0.0 chore(main): release 0.2.0 Aug 28, 2026
@kitchen-porter
kitchen-porter force-pushed the release-please--branches--main--components--busser-bash branch from 1eb334a to 6275aa1 Compare August 28, 2026 21:51
@tas50
tas50 merged commit cefa442 into main Aug 28, 2026
8 checks passed
@tas50
tas50 deleted the release-please--branches--main--components--busser-bash branch August 28, 2026 21:53
@kitchen-porter

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

AsherBond pushed a commit to AsherBond/busser-bash that referenced this pull request Sep 1, 2026
By default release-please reads the "!" on a breaking change as a graduation to
1.0.0, which is what test-kitchen#14 proposed. This is still a 0.x gem, so a breaking change
should take the minor and an ordinary feature should take the patch.

Signed-off-by: Tim Smith <tsmith84@proton.me>
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.

2 participants