Add comment on CloudEvents compliance pending (ref #105) in readiness checklist #106
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
Adds a comment in the API Readiness Checklist regarding CloudEvents compliance (Commonalities r3.3). This documents the current gap and references the issue tracking its resolution, ensuring transparency and alignment with Release Management requirements.
Which issue(s) this PR fixes:
Fixes #105
Special notes for reviewers:
This PR only updates documentation (readiness checklist). No functional or OAS changes are included. The actual fix will be handled in a later release (v0.2.0) as tracked in the referenced issue.
Changelog input
Additional documentation
This section can be blank.
N/A