PredictiveConnectivityData r1.2 (Fall25 M4) release review

[Kevsy]

Release PR to review

• Release r1.2 (Fall'25 M4) PredictiveConnectivityData#34

Related release tracker pages in wiki

• https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/125174076/predictive-connectivity-data+v0.1.0

Review actions

API repository

• Check that there are no PRs beside the release PR are waiting to be reviewed and merged. If there are other open PRs, request that they are either set to draft (if not relevant for Fall25) or merged and the release PR get updated before the review

CHANGELOG.MD

Table of contents

• the y in rX.Y has been increased by 1 from the pre-release

Release notes

• first paragraph: 'public release' is used instead of 'pre-release'
• the release candidate suffix (-rc.x) has been removed from API versions
• the release candidate suffix (-rc.x) has been removed from Commonalities and ICM versions

API sections of CHANGELOG

• the words 'release candidate' are not present
• the release candidate suffix (-rc.x) has been removed from API versions
• API definition links {ReDoc, Swagger, OAS) includes the correct release tag in the URL
• Added/Changed/Removed sections includes any additional changes made for M4 and all the entries from M3
• Note: create a "draft release" to see which PRs were done since the last document pre-release rX.Y

API definition .yaml file(s)

• info.version has been updated to latest version number (without rc.n suffix)
• info.servers.url has been updated to include latest version number (without rc.n suffix)
• check for links containing /main/ or /rX.Y/ (with rX.Y being the pre-release) which are pointing to the repository. They must be replaced with the /rX.Y+1/.
• check that any properties with date-time format reference RFC 3339 in their description, and suggest to delete the additional format recommendation if still present (was removed in r3.3 of API Design Guide, see Commonalities #497).
• Read the Swagger UI view of the API yaml to spot formatting/spelling errors

Test definition .feature file(s)

• 'Feature:' line: vwip has been changed to the latest version number
• All resource links have been updated with the correct serverURL and are using a root-relative path (e.g. And the resource "/qos-profiles/v1/qos-profiles/{name}")

API Readiness checklist

• first line ('Checklist for'): has been updated to the latest version number and the latest release number
• links to Commonalities and ICM r3.3
• for stable APIs Test result statement is mandatory - issue link should be referenced

README.MD

• the 'NEW: public release' section is updated with the latest release number
• The ReDoc/Swagger/OAS links have been updated with the latest release number in their URL
• the 'NEW: Pre-release' section has been removed

API description wiki page

• Check that the links within API Readiness Checklists are pointing to valid wiki pages
• Co-assign the review issue to a member of the API Backlog team (tbd to whom!)
• Get confirmation from API Backlog team that the API description is up-to-date

Release actions

Assign this issue to yourself or another RM team member and follow the below list.
When done, tick the box in this issue (requires write access, leave a comment otherwise).

• Short link to release review issue added to release trackers ("M4 #nnn")
• Review comments provided (on behalf of Release Management)
• Review comments addressed (by release PR editor)
• Check there are no additional errors from centralised linting (ref Linting rules update Commonalities#502)
• /rc-api-review run by Release Management reviewer as final check
• Release PR approved (on behalf of Release Management)
• PR merged (by API repository codeowner)
• Release created within GitHub (by API repository codeowner)
• Release Tracker updated (with creation date of the release and the release tag link)

(Note: For public releases within Fall25 M4 the updates of GitHub README, CAMARA website and within API Backlog list will be done in batch as part of M5 milestone.)

Additional comments

[albertoramosmonagas]

✅ Confirmation – PredictiveConnectivityData | API Backlog Alignment

• - The review issue for PredictiveConnectivityData has been co-assigned to a member of the API Backlog team.
• - The API Backlog team has confirmed that the API description is up-to-date.

Ready to proceed with the next steps in the Release Management process.

[bigludo7]

@hdamker I was ready to take this one but noticed:

hdamker reviewed on behalf of https://github.com/orgs/camaraproject/teams/release-management_reviewers last week (last week)

So I guess you started the review of this one?

[hdamker]

So I guess you started the review of this one?

@bigludo7 no, that was just a finding by chance which I commented. If I started a complete review I assign the review issue to me.

[bigludo7]

/rc-api-review

[github-actions]

🤖 Release Candidate Review Triggered

Starting automated CAMARA API review...

Details:

• Pull Request: Release r1.2 (Fall'25 M4) PredictiveConnectivityData#34
• Review Type: release-candidate
• Commonalities Version: 0.6
• Repository: camaraproject/ReleaseManagement
• Trigger: /rc-api-review

Version Support:

• ✅ Commonalities 0.6: Fully supported
• ⏳ Commonalities 0.7+: Coming soon

Results will be posted here when the review completes.

[github-actions]

✅ API Review Complete

Triggered by: Comment / by @bigludo7
Pull Request: camaraproject/PredictiveConnectivityData#34
Repository: camaraproject/ReleaseManagement
Review Type: release-candidate
Commonalities Version: 0.6
Workflow Run: 17606848527

Review Summary

❌ Critical Issues Found

APIs Reviewed:

• 📧 predictive-connectivity-data v0.1.0 (Implicit Subscription API)

Issues Summary:

• 🔴 Critical: 1
• 🟡 Medium: 0
• 🔵 Low: 1

Issues Requiring Attention:

🔴 Critical Issues (1):

• predictive-connectivity-data: Security Schemes - Subscription APIs must include 'notificationsBearerAuth' security scheme

Recommendation: ❌ Address 1 critical issue(s) before release

📄 Detailed Report: api_review_PredictiveConnectivityData_comment288_v0_6_20250910_074428.md - Direct download

📄 Download: Available as workflow artifact for complete analysis

🔍 Validation: This review includes subscription type detection, scope validation, filename consistency, schema compliance, project consistency, and test alignment validation

---

Workflow Information:

• Validator: api_review_validator_v0_6.py
• Duration: 0s
• APIs Found: 1
• Workflow Run: 398

Next Steps

⚠️ 1 critical issue(s) found - Please address before release.

1. Review the detailed report in the workflow artifacts
2. Fix all critical issues
3. Re-run the review with /rc-api-review

[bigludo7]

/rc-api-review

[github-actions]

🤖 Release Candidate Review Triggered

Starting automated CAMARA API review...

Details:

• Pull Request: Release r1.2 (Fall'25 M4) PredictiveConnectivityData#34
• Review Type: release-candidate
• Commonalities Version: 0.6
• Repository: camaraproject/ReleaseManagement
• Trigger: /rc-api-review

Version Support:

• ✅ Commonalities 0.6: Fully supported
• ⏳ Commonalities 0.7+: Coming soon

Results will be posted here when the review completes.

[github-actions]

✅ API Review Complete

Triggered by: Comment / by @bigludo7
Pull Request: camaraproject/PredictiveConnectivityData#34
Repository: camaraproject/ReleaseManagement
Review Type: release-candidate
Commonalities Version: 0.6
Workflow Run: 17612589039

Review Summary

✅ Ready for Release

APIs Reviewed:

• 📧 predictive-connectivity-data v0.1.0 (Implicit Subscription API)

Issues Summary:

• 🔴 Critical: 0
• 🟡 Medium: 0
• 🔵 Low: 1

Recommendation: ✅ Approved for release

📄 Detailed Report: api_review_PredictiveConnectivityData_comment288_v0_6_20250910_114116.md - Direct download

📄 Download: Available as workflow artifact for complete analysis

🔍 Validation: This review includes subscription type detection, scope validation, filename consistency, schema compliance, project consistency, and test alignment validation

---

Workflow Information:

• Validator: api_review_validator_v0_6.py
• Duration: 0s
• APIs Found: 1
• Workflow Run: 410

Next Steps

🎉 No critical issues found - API is ready for release!

[hdamker]

All done here