Conversation
- target_release_tag r1.1 -> r1.2, target_release_type pre-release-rc - commonalities_release r4.3 -> r4.4 (0.9.0); ICM stays r4.2 - api_name media-streaming-rate -> device-media-streaming-rate, target_api_status alpha -> rc, target_api_version 0.1.0
CAMARA Validation — FAIL1 errors, 0 warnings, 0 hints | Profile: standard |
maheshc01
added a commit
that referenced
this pull request
Sep 14, 2026
Align the API name with the repository name (#38): - API definition file renamed to device-media-streaming-rate.yaml - info.title, tags, servers.url, security scope, schema names and description references updated accordingly - Test definitions renamed to device-media-streaming-rate.feature with matching resource path and scenario tags release-plan.yaml is updated separately in #48, as the validation rules require release-plan changes to be in their own PR.
Contributor
Author
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
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.
What type of PR is this?
What this PR does / why we need it:
Declares the r1.2 release candidate in
release-plan.yaml, following the r1.1 alpha published on 2026-09-14 and the request in #35 to prepare an rc that incorporates Commonalities r4.4:target_release_tag: r1.1 → r1.2target_release_type: pre-release-alpha → pre-release-rccommonalities_release: r4.3 → r4.4 (0.9.0); ICM stays r4.2api_name: media-streaming-rate → device-media-streaming-rate (repository/API name alignment, Repository name does not match API name #38)target_api_status: alpha → rc,target_api_versionstays 0.1.0 (expected rc version 0.1.0-rc.1)Which issue(s) this PR fixes:
Related to #37 and #38. No issue is closed by this PR.
Special notes for reviewers:
release-plan.yaml, as required by the validation rule P-022.device-media-streaming-rate.yamlis in a separate PR. The validation rules require the release plan and the file name to match (P-002 / P-009) and also require release-plan changes to be in their own PR (P-022), so the rename PR and this PR cannot both be green while the other is unmerged. Intended order: content PR Address r1.1 review findings in the API definition and test definitions #47, then the rename PR, then this PR. Once the rename is onmainthis PR is re-run and the P-009 finding disappears.code/common/to r4.4. The switch of the API definition to the r4.4 error response catalogue follows in a further PR once that sync has landed.Changelog input
Additional documentation