feat: add message-level versioning support to Message Object #1140
Conversation
This file contains hidden or 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
h30s
requested review from
GreenRover,
asyncapi-bot-eve,
char0n,
dalelane,
derberg and
fmvilas
as code owners
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add Message-Level Versioning Support to AsyncAPI 3.0.0
This PR introduces optional
nameandversionfields to the Message Object, enabling granular message-level versioning while maintaining full backward compatibility.What’s Included
nameandversionfields to the Message and Message Trait Objectsversionrequiresname, preserving clear message identityWhy
AsyncAPI previously supported versioning only at the application level, causing:
This change enables clear evolution of individual messages and unlocks richer tooling capabilities (diffing, timelines, compatibility checks).
Validation
100% backward compatible
Clear validation rules:
name+version→ ✅name→ ✅version→ ❌Comprehensive tests and documentation included.
Related
Closes #1068.