feat!: add 3.0.0 validation support #462
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: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>%0ACo-authored-by: Florent Baldino <[email protected]>%0ACo-authored-by: asyncapi-bot <[email protected]>
Co-authored-by: Fran Méndez <[email protected]>
Co-authored-by: Sergio Moya <[email protected]>
jonaslagoni
requested review from
fmvilas,
derberg,
dalelane,
smoya,
char0n and
asyncapi-bot-eve
as code owners
|
This PR is a duplicate of #208 as it was incorrectly merged. |
derberg
approved these changes
Nov 30, 2023
|
SonarCloud Quality Gate failed.
|
|
/rtm |
|
🎉 This PR is included in version 6.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
smoya
added a commit
that referenced
this pull request
Dec 4, 2023
Co-authored-by: Sergio Moya <[email protected]> Co-authored-by: Fran Méndez <[email protected]> Co-authored-by: Lukasz Gornicki <[email protected]> Co-authored-by: Maciej Urbańczyk <[email protected]>
smoya
added a commit
that referenced
this pull request
Dec 4, 2023
Co-authored-by: Sergio Moya <[email protected]> Co-authored-by: Khuda Dad Nomani <[email protected]> Co-authored-by: Ace <[email protected]> Co-authored-by: Fran Méndez <[email protected]> Co-authored-by: Jeremy Whitlock <[email protected]> Co-authored-by: Laurent Broudoux <[email protected]> Co-authored-by: Lukasz Gornicki <[email protected]> Co-authored-by: Maciej Urbańczyk <[email protected]>
|
🎉 This PR is included in version 6.0.0-next-major-spec.17 🎉 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.
When this is merged, from version 6 and onwards, all pre-release spec versions will be released as a regular feature request, before the spec itself is released.
The pre-release version will be released as if it was not a pre-release, for example for AsyncAPI 3.0, it will be released as normal:
However, while the it's still a pre-release, the underlying schemas CAN contain breaking changes from version to version, up until the spec is released. This means that one AsyncAPI document using v3 in the pre-release stage might be valid in
6.0.0, but invalid in the6.1.0. This ONLY applies to pre-release schemas, and NOT regular ones that is set in stone.If you want to make sure you don't use a schema not released yet, you have to whitelist which versions you allow in your tool.
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.