-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
chore(main): release 0.5.0 #28
Conversation
Release candidate v0.4.1-rc.1 published. |
ed4af0a
to
3d67993
Compare
Release candidate v0.4.1-rc.2 published. |
3d67993
to
34680eb
Compare
Release candidate v0.4.1-rc.3 published. |
34680eb
to
1f64e81
Compare
1f64e81
to
92b7b2c
Compare
Release candidate v0.5.0-rc.4 published. |
Mistake there - the CI bump should have been a fix or a chore: |
92b7b2c
to
6dc5f03
Compare
Release candidate v0.5.0-rc.5 published. |
@J0 Maybe you could revert the PR, then re-add it with a fixed title. I think Release Please is smart enough to detect this? |
Sure let's try that now |
Opened one here - #44 is there a dedicated semantic prefix for reverts? |
6dc5f03
to
0e6adda
Compare
0e6adda
to
5095bf5
Compare
Release candidate v0.5.0-rc.7 published. |
5095bf5
to
4ba176a
Compare
Release candidate v0.5.0-rc.8 published. |
🤖 Created releases:
|
🤖 I have created a release beep boop
0.5.0 (2024-08-19)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.