Fix stale API Readiness Checklist pointer in mandatory error-response template - #693
Open
hdamker wants to merge 1 commit into
Open
Conversation
hdamker
requested review from
PedroDiez,
bigludo7,
eric-murray,
jlurien and
rartych
as code owners
August 4, 2026 10:52
eric-murray
approved these changes
Aug 5, 2026
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
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?
What this PR does / why we need it:
Repoints the mandatory
additional-error-responsesinfo.descriptiontemplate's second sentence — which named the retired per-APIAPI Readiness Checklistdocument — at sources that exist on every current release: thex-camara-commonalitiesfield, the changelog, and the release metadata.Updated in all 5 locations carrying the sentence verbatim:
documentation/CAMARA-API-Design-Guide.md§3.2.3artifacts/common/info-description-templates.yamlartifacts/api-templates/sample-service.yamlartifacts/api-templates/sample-implicit-events.yamlartifacts/api-templates/sample-service-subscriptions.yamlWhich issue(s) this PR fixes:
Fixes #692
Does this PR introduce a breaking change?
Special notes for reviewers:
Wording open for discussion — happy to adjust before merge.
Changelog input
Additional documentation
This section can be blank.