-
-
Notifications
You must be signed in to change notification settings - Fork 280
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
chore: update next-spec
with latest master
#892
Conversation
Co-authored-by: Sergio Moya <[email protected]> Co-authored-by: Maciej Urbańczyk <[email protected]> Co-authored-by: Jeremy Whitlock <[email protected]> Co-authored-by: Lukasz Gornicki <[email protected]>
Co-authored-by: asyncapi-bot <[email protected]>
Co-authored-by: asyncapi-bot <[email protected]> Co-authored-by: Lukasz Gornicki <[email protected]>
Co-authored-by: asyncapi-bot-eve <[email protected]> Co-authored-by: asyncapi-bot <[email protected]> Co-authored-by: Lukasz Gornicki <[email protected]>
…lows/scripts/mailchimp (#867)
Kudos, SonarCloud Quality Gate passed! |
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.
👍 Let's make sure we merge this one with the Merge commit strategy instead of the Squash and Merge one, to avoid future conflicts.
🎉 This PR is included in version 2.5.0-next-spec.5 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 2.6.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 3.0.0-next-major-spec.18 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This is just a typical update of release branch with latest changes from master.
There was only once merge conflict I had to solve related to
.github/workflows/if-nodejs-release.yml
. This file was removed frommaster
and I had to enforce it onnext-spec
branch