Repository navigation
update the release-plan file for the Sync26 release. - #12
Closed
ChinaUnicomXiaoDongrui wants to merge 4 commits into
Closed
ChinaUnicomXiaoDongrui wants to merge 4 commits into
ChinaUnicomXiaoDongrui wants to merge 4 commits into
Annotations
3 errors and 2 notices
|
|
|
|
|
release-plan.yaml#L1
[P-022] release-plan.yaml was changed alongside 1 other file(s)%3A code/API_definitions/esim-remote-management.yaml. release-plan.yaml changes should be submitted in a dedicated PR so that any new validation findings remain clearly attributable to the release-plan change. | Suggestion%3A Split this PR%3A keep release-plan.yaml changes in a dedicated PR, and move the other listed files to a separate PR.
|
|
code/Test_definitions#L1
[P-006] No .feature test file found for API 'esim-remote-management' in code/Test_definitions/ | Suggestion%3A Test files are optional for alpha releases but expected before the first release candidate. On stable (>=1.x) APIs they are required at rc and public release; on initial (0.x) APIs they are strongly recommended. See CAMARA Testing Guidelines for the expected file layout.
|
|
code/API_definitions/esim-remote-management.yaml#L1
[P-002] Expected spec file 'code/API_definitions/esim-remote-management.yaml' not found — check that api_name 'esim-remote-management' in release-plan.yaml matches the actual filename | Suggestion%3A Spec file not yet present. For draft entries this is acceptable; add the spec file before advancing target_api_status to alpha.
|
The logs for this run have expired and are no longer available.
Loading