Release Review: DeviceRoamingStatus r2.1 (rc Sync26)

[camara-release-automation]

Release Review: r2.1 rc

This PR finalizes the reviewable release content for the active snapshot.

Edit and review this PR before merging it into the release snapshot. After Codeowner and Release Management approval, merging this PR creates the draft release.

Release contents

API	Version	Status	Comparison target
device-roaming-status-subscriptions	0.9.0-rc.1	rc	0.8.0
device-roaming-status	1.2.0-rc.3	rc	1.1.0

Dependencies: Commonalities r4.3, ICM r4.2

Codeowner Actions

Tick each box once done. Release Management review starts when all three boxes are ticked.

• Update the CHANGELOG

  What to do:

  • Copy all API-consumer-relevant changes from the provided list into the appropriate Breaking changes / Added / Changed / Fixed / Removed sections for each API. List breaking changes both in Breaking changes and in their normal change category.
  • Do not copy administrative, tooling-only, or internal maintenance changes unless they affect API consumers.
  • For each API, fill the CHANGELOG against the stated comparison target, following the release-type rules at the top of the CHANGELOG.

• Document deferred validation warnings (and hints)

  What to do:

  • Check the CAMARA Validation comment on this PR for warnings and hints.
  • For each warning you do not fix, document it in an issue: include a copy of the validation summary line(s) and the reason the fix is deferred.
  • Document in the same way any validation hint that is applicable to the API and needs to be fixed later.
  • You may group several findings into one issue or split them across issues — either is fine.
  • List the documenting issue(s) in a comment on this PR.
  • Note: documenting deferred warnings is optional but recommended for alpha pre-releases, and mandatory for rc pre-releases and public releases.

• The release is ready for Release Management review

  Check that:

  • All mandatory release assets for the declared status(es) are present (see the table below "Required release assets per API status" by expanding the arrow);
  • API documentation and test cases are adequate for the target status.

  Tick this box to confirm readiness and to start the Release Management review.

Release Management Actions

• CHANGELOG follows the release documentation rules
• Breaking changes are documented and version updates follow SemVer rules
• Mandatory release assets are present for each API according to its status
• All remaining validation warnings are documented in issues and the reasons for deferral are defensible

Required release assets per API status

Nr	Asset	alpha	rc	initial public	stable public
1	Release Plan	M	M	M	M
2	API Definition(s)	M	M	M	M
3	Commonalities compliance	O	M	M	M
4	API Documentation	M	M	M	M
5	User Stories	O	O	O	M
6	Test Cases (basic)	O	M	M	M
7	Test Cases (enhanced)	O	O	O	M
8	API Description	O	O	M	M

M = Mandatory, O = Optional — Full documentation

Valid next actions for codeowners

• Merge this PR when all Codeowner Actions and Release Management Actions are complete and the required approvals are present — creates the draft release
• Use /discard-snapshot <reason> in the Release Issue to discard this snapshot, return to planned, and update content on main

---

Snapshot: r2.1-9be6fb2

[camara-validation]

CAMARA Validation — PASS

0 errors, 0 warnings, 3 hints | Profile: standard

View full results

NA

[hdamker]

The device-roaming-status-subscriptions CHANGELOG entry doesn't fully describe what changed in GET /subscriptions.

Comparing 0.8.0 (last released, in r1.2) to 0.9.0-rc.1, the response body for GET /subscriptions changed from a plain array of Subscription to a wrapper object { subscriptions: [...], pagination: {...} }, and the operation gained page/perPage query parameters plus X-Total-Count / X-Total-Pages / Link response headers. This came in via #78 ("Update API definitions to fix CAMARA validation warnings and hints").

Two things to fix in CHANGELOG-r2.md:

1. Changed already lists #78 ("Update API definitions to fix CAMARA validation warnings and hints"), but only as that generic one-liner. Please expand it to spell out what actually changed for consumers: GET /subscriptions now supports pagination — new page/perPage query parameters, new X-Total-Count/X-Total-Pages/Link response headers, and the response body changed from a bare array to a { subscriptions: [...], pagination: {...} } object.
2. Breaking changes is currently N/A. The response-shape change above is breaking for any consumer of 0.8.0 (bare array → wrapped object). Since device-roaming-status-subscriptions is still pre-public (0.x), this is allowed without a major bump — but the release documentation rules ask that breaking changes be listed both under Breaking changes and under their normal category (here, Changed), not marked N/A.

[hdamker]

Beyond the previous comment on the CHANGELOG I have created #93 - not blocking for the first rc, but should be addressed and provided in a second rc.

[hdamker]

Looks good now from ReleaseManagement perspective, thanks @eric-murray