Sync common files from Commonalities r4.3

[camara-release-automation]

Warning

This branch is owned by Release Automation and is rebuilt from main on every run.
Do not commit fixes to this branch — any commits here are overwritten the next time the sync runs.

Automated sync of code/common/ files from camaraproject/Commonalities at release tag r4.3.

This PR was created by release automation because the cached Commonalities files were out of sync with the declared dependency in release-plan.yaml.

What changed:

• Updated files in code/common/ to match Commonalities r4.3
• Added/updated .sync-manifest.yaml with file integrity hashes

How to handle this PR:

• Validation green — review and merge.
• Validation red — choose one:
  • (recommended) fix the errors on main, then re-trigger the sync; this PR is rebuilt from the new main HEAD with the corrected content.
  • merge this PR with the errors and fix them on main afterwards.

To re-trigger the sync, run the CAMARA Release Automation workflow from the repository's Actions tab.

/create-snapshot is blocked until common files are in sync.

[camara-validation]

CAMARA Validation — PASS (with warnings)

0 errors, 16 warnings, 1 hints | Profile: standard

View full results

[ToshiWakayama-KDDI]

Hi @chinaunicomyangfan , @ClownsAlbert , @ChuanyuChen , @DanXu-ChinaTelecom ,
As you can see, Subscription Status API has passed the validation:
CAMARA Validation — PASS (with warnings)
0 errors, 16 warnings, 1 hints | Profile: standard

Therefore, you guys can approve and merge this PR, and then you can sort the 16 warnings & 1 hint out. As shown in "Files Changed", this PR will copy four common artifacts to "code/common" in the SubscriptionStatus repository. If these four artifacts do not exist, you can't remove the warnings and hint, which is required for Sync26 meta-release. Please do a quick review of this PR and approve & merge it.

Thanks,
Toshi

[ToshiWakayama-KDDI]

Hi @chinaunicomyangfan , @ClownsAlbert , @ChuanyuChen , @DanXu-ChinaTelecom ,

As you are aware, today, June 30th, is the M3 deadline (for the first release-candidate API version for Sync26, created by a release candidate PR).

If you intend to target Sync26, could you please review, approve, and merge this PR as soon as possible? This will allow you to proceed with the next steps in the release candidate process.

Many thanks,
Toshi

[chinaunicomyangfan]

LGTM

[chinaunicomyangfan]

Hi @ToshiWakayama-KDDI ,Thank you for your remind.I have merged this PR. Is there anything else I need to do？

[ToshiWakayama-KDDI]

Thanks, @chinaunicomyangfan . Well, regarding what you need to do, please review our bi-weekly meeting minutes ("schedule for next releases") and what other APIs are doing, but I could advise you briefly that there are two types of activities for Sync26 meta-release:

1. Clear the warnings and hints detected by Release Automation Validation. Above in this PR, you can see "CAMARA Validation - PASS (with warnings)" part and if you click View full results, you will see what warnings and hints you have to clear. Create separate PR.

2. Get the API specification (yaml) aligned with the latest Commonalities/ICM. Please check other APIs' Issues/PRs related to this, such as 'Alignment with Guidelines and linting rules for OWASP API Security Top 10' and 'Commonalities 8.0.0 alignment and fix validation warnings'.

I should be able to support you, once I have completed Match, Fill-in, and Age Verification. I am working on them, together with Gilles.

Thanks,