Public Release for Fall24 meta-release

[PedroDiez]

What type of PR is this?

Add one of the following kinds:

• bug
• correction
• documentation
• subproject management

What this PR does / why we need it:

PR to generate Public Release of Carrier Billing Checkout Family APIs

Which issue(s) this PR fixes:

Fixex #155
Fixes #168
Fixes #173
Fixes #175

Special notes for reviewers:

PRs #174 and #176 to be merged first than this one

Changes driven in API Spec YAMLs:

• Apply File Name conventions (kebab-case)
• Adjustment of version and servers values
• Adjustment externalDocs link
• Adjustment sink Description
• Fix missing required request Body in confirmPayment operation
• Fix 401 Error with Commonalities and also align the model of Errors with Commonalities "CAMARA_common.yaml" naming. - - Remove 400 PhoneNumber Required as Covered by 422 Exception

Changelog input

Public Release of Carrier Billing Family APIs for MetaRelease Fall24

Additional documentation

N/A

[bigludo7]

LGTM - Thanks @PedroDiez
Up to @hdamker and the release Management team ;)

[hdamker]

@PedroDiez If you want to have the meeting soon within main, you may want to do it in an own PR. Could take some days before the release PR gets approved by the RM team.

[jlurien]

• API Readiness checklists should be updated to r1.2 versions (without -rc suffixes), and resolve any pending tbd

[PedroDiez]

@PedroDiez If you want to have the meeting soon within main, you may want to do it in an own PR. Could take some days before the release PR gets approved by the RM team.

Thanks Herbert, I will comment tomorrow in the WG meeting. I think we can wait because relevant people is already aware of new schedule

[jlurien]

Some projects are naming User stories with the same format than API-Readiness-Checklist, that is api-name-User-Story.md, but it is not made a requirement

[PedroDiez]

Some projects are naming User stories with the same format than API-Readiness-Checklist, that is api-name-User-Story.md, but it is not made a requirement

Thanks @jlurien I am applying it, It is fine to align

[jlurien]

Approved on behalf of Release Management

[bigludo7]

LGTM

[PedroDiez]

After TSC meeting, it can be merged:

SC Approval of M4 (all release PRs of Sub Project reviewed by Release Management)

• We can merge PR when review completed
• M4 Release tracker date: date when the merged is done by the project