-
-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: release for version 2.4.0 of the spec #185
Conversation
/dnm |
/autoupdate |
Even though #184 is going to be merged very soon, and all the opened PR's for 2.4 are using the one-file json schema version, we would need to adapt all the changes into the new file structure. |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
@@ -1,6 +1,6 @@ | |||
{ | |||
"name": "@asyncapi/specs", | |||
"version": "2.13.2", | |||
"version": "2.14.0-2022-04-release.3", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be probably changed to the 2.13.2
"version": "2.14.0-2022-04-release.3", | |
"version": "2.13.2", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, RC should stay, semantic-release
will figure it out, notice 2.13 and bump to 2.14 🍻
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great ❤️
Only @dalelane approval is left and Ok to go! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(sorry for the delay!)
/rtm |
🎉 This PR is included in version 2.14.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 3.0.0-next-major.5 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This PR is created upfront to reflect on a daily basis what things are included in the release.
Also, the reason to create this PR a long time before the release is to enable automation (bot keeps upstream branches always up to date with master, see this action) that we have in place to regularly update the release branch with whatever is changed in the master branch. So nobody has to do it manually.