Release r3.1 (RC) — Sync26

[camara-release-automation]

Content scope

This RC consolidates the work done since the r2.1 alpha (Sync26) under two themes:

1. Validation & Commonalities conformance. Cleared the findings surfaced by the new CAMARA Validation Framework and aligned to Commonalities r4.3 / ICM r4.2: moved non-spec files out of API_definitions/ (#134), added 400 input-validation responses to all read/delete operations (#133), tightened integer format/bounds and string maxLengths (#135), and added array maxItems plus the mandatory info.description template blocks (#155). The spec now passes validation with 0 errors / 0 warnings.

2. API split. Split the single network-access-management API into two cohesive APIs (#152): network-access-devices (/network-access-devices, /reboot-requests) and network-access-domains (/trust-domains, /trust-domains/{id}/devices, /services), staged as release-plan-only steps to keep main clean throughout. The info.description was refactored to the new two-API structure and a Trust Domain device-registration user story added (#143). Both APIs ship at 0.3.0-rc.1.

Scope issues: #134, #133, #135, #155, #152, #143.

Preparing the release content

Before issuing /create-snapshot, verify on main:

• release-plan.yaml content matches intent (check API names, versions, statuses, release type)
• Commonalities and ICM dependency versions are current
• CI checks are green (Spectral linting, PR validation)
• All intended implementation PRs are merged
• SemVer is correct (breaking changes only in v0.x initial or new major versions)
• Release assets provided for declared API status(es)

Required release assets per API status (see full documentation)

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

---

Release Status

State: snapshot-active | Last Updated: 2026-06-29T21:23:39Z

Active snapshot: r3.1-99c6b06
Release PR: #164

Release type: rc

API	Status	Target	Calculated
network-access-devices	rc	0.3.0	0.3.0-rc.1
network-access-domains	rc	0.3.0	0.3.0-rc.1

Dependencies: Commonalities r4.3 (0.8.0), ICM r4.2 (0.5.0)

Valid actions:
→ Update, review, and merge Release PR to create draft release
→ /discard-snapshot <reason> — discard and return to planned

[camara-release-automation]

📋 Release issue created — State: planned

Configuration: Release r3.1 (rc, Sync26)

API	Version
network-access-management	0.3.0

Dependencies: Commonalities r4.3, ICM r4.2

Valid actions (post a comment):
→ /create-snapshot — begin the release process

[camara-release-automation]

Common file sync: sync PR created
Commonalities: expected r4.3, manifest has r4.2

The cached Commonalities files in code/common/ are out of sync with r4.3 declared in release-plan.yaml. A sync PR has been created to update them.

Action required: Review and merge the sync PR. /create-snapshot is blocked until common files are in sync.

[clundie-CL]

/create-snapshot

[github-actions]

✅ Snapshot created — State: snapshot-active
Release PR: #147 · Snapshot: r3.1-a911a36

Configuration: Release r3.1 (rc, Sync26)

API	Version
network-access-management	0.3.0-rc.1

Dependencies: Commonalities r4.3, ICM r4.2

Valid actions:
→ Update, review, and merge Release PR to create draft release
→ /discard-snapshot <reason> — discard and create a new snapshot from updated main

[clundie-CL]

/discard-snapshot Previous create-snapshot was just a test

[github-actions]

🗑️ Snapshot discarded — State: planned
Reason: Previous create-snapshot was just a test
Preserved: release-review/r3.1-a911a36-preserved · Deleted: snapshot branch, Release PR closed

Configuration: Release r3.1 (rc, Sync26)

API	Version
network-access-management	0.3.0-rc.1

Dependencies: Commonalities r4.3 (0.8.0), ICM r4.2 (0.5.0)

Valid actions:
→ /create-snapshot — new snapshot from updated main