Release r1.2 (Fall'25 M4)

[eric-murray]

What type of PR is this?

• subproject management

What this PR does / why we need it:

Publication of Fall'25 M4 public release of:

• connected-network-type v0.2.0
• connected-network-type-subscriptions v0.2.0

Which issue(s) this PR fixes:

Fixes #36

Special notes for reviewers:

None

Changelog input

 release-note
 - Publication of Fall'25 M4 public release of connected-network-type v0.2.0 and connected-network-type-subscriptions v0.2.0

Additional documentation

None

[bigludo7]

Hello @eric-murray
We probably need to apply requested modifications listed here: https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/198443045/Analysis+of+Commonalities+0.6.0 and in particular:

• ErrorInfo scheme unification in CAMARA_common.yaml and event-subscription-template.yaml #506 --> update of ErrorInfo message & status description
• Changed Mandatory Description for date-time string format and updated template files #497 --> test shortened

[eric-murray]

@bigludo7
Yes, that's fine, but should be done as a separate PR, and not as part of this one.

If other PRs cause merge conflicts with this one, I will fix them

[rartych]

L426 in connected-network-type-subscriptions.yaml is not valid anymore (API sub-projects are free to decide to allow more than one event type per subscription.)

Note: For the current Commonalities API design guidelines, only one event type per subscription is allowed, yet in the following releases use of array of event types SHALL be specified without changing this definition.

[rartych]

In connected-network-type-subscriptions.yaml (lines 466-475) the text:

Up to API project decision to keep it.

is not needed.

[rartych]

Is using square brackets [] intended here:

ConnectedNetworkType/code/API_definitions/connected-network-type-subscriptions.yaml

Line 25 in 86cd1e8

- `UNKNOWN`: if connection [technology] can not be determined

[rartych]

Please review suggested changes

[rartych]

Device status server in connected network type API, is it correct:

ConnectedNetworkType/code/API_definitions/connected-network-type-subscriptions.yaml

Line 166 in 86cd1e8

The Device status server will call this endpoint whenever the connected network type of the device changes.

[bigludo7]

Thanks @rartych for the review.

All fixed :)

[hdamker]

Please address the link to Commonalities r2.3 into the deprecated API Design Guideline Document. See camaraproject/Commonalities#531 for further background and potential short-term solution.

ConnectedNetworkType/code/API_definitions/connected-network-type-subscriptions.yaml

Line 729 in 6fe9e64

description: The unique identifier of the subscription in the scope of the subscription manager. When this information is contained within an event notification, this concept SHALL be referred as `subscriptionId` as per [Commonalities Event Notification Model](https://github.com/camaraproject/Commonalities/blob/r2.3/documentation/API-design-guidelines.md#122-event-notification).

cc: @bigludo7

[bigludo7]

Please address the link to Commonalities r2.3 into the deprecated API Design Guideline Document. See camaraproject/Commonalities#531 for further background and potential short-term solution.

ConnectedNetworkType/code/API_definitions/connected-network-type-subscriptions.yaml

Line 729 in 6fe9e64

description: The unique identifier of the subscription in the scope of the subscription manager. When this information is contained within an event notification, this concept SHALL be referred as `subscriptionId` as per [Commonalities Event Notification Model](https://github.com/camaraproject/Commonalities/blob/r2.3/documentation/API-design-guidelines.md#122-event-notification).

cc: @bigludo7

Fixed by replacing with a description without link.

Request changes is done

[rartych]

Approved on behalf of Release Management