chore: update next-spec with latest master
#301
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Sergio Moya <[email protected]>
…lows/scripts/mailchimp (asyncapi#282)
…capi#288) Co-authored-by: Lukasz Gornicki <[email protected]>
derberg
requested review from
fmvilas,
dalelane and
asyncapi-bot-eve
as code owners
|
Kudos, SonarCloud Quality Gate passed!
|
fmvilas
approved these changes
Jan 17, 2023
dalelane
approved these changes
Jan 17, 2023
36 tasks
|
🎉 This PR is included in version 3.3.0-next-spec.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 4.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 5.0.0-next-major-spec.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 5.0.0-next-major-spec.10 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this is just a merge of master into release branch for 2.6 release.
simple merge of master onto next-spec
no merge conflicts. Basically all the commits from the master after 2.5 release