Skip to content

Release Review: DeviceLocation r4.1 (rc Sync26) - #415

Closed
camara-release-automation[bot] wants to merge 2 commits into
release-snapshot/r4.1-b156e68from
release-review/r4.1-b156e68
Closed

Release Review: DeviceLocation r4.1 (rc Sync26)#415
camara-release-automation[bot] wants to merge 2 commits into
release-snapshot/r4.1-b156e68from
release-review/r4.1-b156e68

Add CHANGELOG draft for r4.1

768e5f1
Select commit
Loading
Failed to load commit list.
camara-validation / CAMARA Validation succeeded Jul 27, 2026 in 0s

0 errors, 5 warnings, 5 hints

Profile: standard | Branch: release | Trigger: pr

Annotations

Check warning on line 665 in code/API_definitions/geofencing-subscriptions.yaml

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

Component may be unused

[S-211] Potentially unused component has been detected.

Suggestion: Remove the component if it is obsolete, or reference it from the API definition.

Check warning on line 667 in code/API_definitions/geofencing-subscriptions.yaml

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

Component may be unused

[S-211] Potentially unused component has been detected.

Suggestion: Remove the component if it is obsolete, or reference it from the API definition.

Check warning on line 1112 in code/API_definitions/geofencing-subscriptions.yaml

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

Schema name must be PascalCase

[S-015] CloudEvent-2 should be PascalCase (UpperCamelCase)

Check warning on line 1287 in code/API_definitions/geofencing-subscriptions.yaml

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

Component may be unused

[S-211] Potentially unused component has been detected.

Suggestion: Remove the component if it is obsolete, or reference it from the API definition.

Check warning on line 0 in code/Test_definitions/geofencing-subscriptions.feature

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

Too many scenarios in feature file

[G-004] Number of scenarios exceeds maximum: 53/50

Check notice on line 585 in code/API_definitions/geofencing-subscriptions.yaml

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

String has no format/pattern/enum

[S-313] Schema of type string should specify a format, pattern, enum, or const.

Suggestion: Acceptable if free-form field or implementation-dependent — no fix needed.

Check notice on line 826 in code/API_definitions/geofencing-subscriptions.yaml

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

String has no format/pattern/enum

[S-313] Schema of type string should specify a format, pattern, enum, or const.

Suggestion: Acceptable if free-form field or implementation-dependent — no fix needed.

Check notice on line 858 in code/API_definitions/geofencing-subscriptions.yaml

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

String has no format/pattern/enum

[S-313] Schema of type string should specify a format, pattern, enum, or const.

Suggestion: Acceptable if free-form field or implementation-dependent — no fix needed.

Check notice on line 1126 in code/API_definitions/geofencing-subscriptions.yaml

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

String has no format/pattern/enum

[S-313] Schema of type string should specify a format, pattern, enum, or const.

Suggestion: Acceptable if free-form field or implementation-dependent — no fix needed.

Check notice on line 1132 in code/API_definitions/geofencing-subscriptions.yaml

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

String has no format/pattern/enum

[S-313] Schema of type string should specify a format, pattern, enum, or const.

Suggestion: Acceptable if free-form field or implementation-dependent — no fix needed.