[camara-release-automation]

Release Review: r2.3 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
dedicated-network-accesses	0.2.0-rc.2	rc	0.2.0-rc.1
dedicated-network-profiles	0.2.0-rc.2	rc	0.2.0-rc.1
dedicated-network	0.2.0-rc.2	rc	0.2.0-rc.1
dedicated-network-areas	0.1.0-rc.2	rc	0.1.0-rc.1

Dependencies: Commonalities r4.4, ICM r4.2

Codeowner Actions

Tick each box once done. Ticking the last box — "The release is ready for Release Management review" — starts the Release Management review.

• 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

The following actions and checks are done by a Release Management reviewer before approving the PR:

• Assign the Release Management reviewer(s) as assignee(s) of this PR
• 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
• Content findings needing a main PR are collected as sub-issues of one issue titled Release r2.3 review findings (see Recording review findings)

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.3-81bcd9d

[camara-validation]

CAMARA Validation — PASS

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

View full results

[tlohmar]

PR #196 (int64 -> int32 limits) is listed as Changed, not Breaking. It only lowers the upper limit on values the API returns and the API provider selects the values.

[hdamker]

CHANGELOG, dedicated-network-accesses 0.2.0-rc.2: oasdiff against r2.2 and the description diff show three consumer-breaking changes that are not listed under Breaking changes:

1. POST /accesses/{accessId}/devices/remove: the request body changed from devices (device objects) to the new required accessDeviceIds. Existing clients get 400.
2. createAccess: when none of the requested devices can be added, the access is no longer created and 422 DEDICATED_NETWORK_ACCESSES.NO_VALID_DEVICE is returned. In 0.2.0-rc.1 the access was created and the failures were reported in results. The entry is currently only under Changed (Adding support for three-legged access token #197).
3. device.phoneNumber is no longer guaranteed in responses: device became optional in AccessDevice (omitted for devices added with a three-legged token), and phoneNumber is no longer required inside it (ValidDevice was replaced by the generic Device). This affects GET /accesses/{accessId}/devices, the notifications and the per-device error results.

Suggest adding these to Breaking changes (and keeping them in their normal category).

Minor: the entries for #179 appear three times (Breaking changes, Added, Changed). One entry per category with its actual content is easier to read.