Skip to content

Release Review: PopulationDensityData r4.2 (rc Sync26) - #148

Closed
camara-release-automation[bot] wants to merge 3 commits into
release-snapshot/r4.2-3171af9from
release-review/r4.2-3171af9
Closed

camara-release-automation[bot] wants to merge 3 commits into
release-snapshot/r4.2-3171af9from
release-review/r4.2-3171af9

Update CHANGELOG/CHANGELOG-r4.md

b57cb1d
Select commit
Loading
Failed to load commit list.
camara-validation / CAMARA Validation succeeded Sep 22, 2026 in 0s

0 errors, 10 warnings, 4 hints

Profile: standard | Branch: release | Trigger: pr

Annotations

Check warning on line 1 in code/API_definitions/population-density-data.yaml

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

CloudEvent type format is wrong

[P-015] No event type enum values found in code/API_definitions/population-density-data.yaml — subscription APIs should define EventType schemas

Suggestion: Define a named event type schema (e.g. ApiEventType) that constrains the CloudEvent `type` value via allOf, rather than inlining the enum directly in CloudEvent.properties.type.enum. See the implicit-events API template in Commonalities artifacts/api-templates/ (tracked in camaraproject/Commonalities#608).

Check warning on line 154 in code/API_definitions/population-density-data.yaml

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

info.description mandatory template content drift

[P-027] info.description template 'additional-error-responses' has drifted from canonical at paragraph 3.
  canonical: Please refer to the `CAMARA_common.yaml` of the Commonalities Release associated to this API version for a complete list of error responses. The applicable C...
  found:     Please refer to the `CAMARA_common.yaml` of the Commonalities Release associated to this API version for a complete list of error responses. The applicable C...
Re-copy the BEGIN..END block from 'code/common/info-description-templates.yaml'.

Suggestion: Re-copy the BEGIN..END block from code/common/info-description-templates.yaml to replace the drifted content; the message identifies the first differing paragraph.

Check warning on line 238 in code/API_definitions/population-density-data.yaml

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

Notification must use application/cloudevents+json

[S-035] Notification callback content type must include 'application/cloudevents+json', found: application/json

Check warning on line 471 in code/API_definitions/population-density-data.yaml

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

Array items must have a description

[S-031] Array items must have a description

Check warning on line 471 in code/API_definitions/population-density-data.yaml

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

Schema property must have a description

[S-011] Property description is missing or empty: "TimedPopulationDensityData.description" property must be truthy

Check warning on line 505 in code/API_definitions/population-density-data.yaml

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

Schema property must have a description

[S-011] Property description is missing or empty: "dataType.description" property must be truthy

Check warning on line 520 in code/API_definitions/population-density-data.yaml

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

Schema property must have a description

[S-011] Property description is missing or empty: "NoData.description" property must be truthy

Check warning on line 523 in code/API_definitions/population-density-data.yaml

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

Schema property must have a description

[S-011] Property description is missing or empty: "LowDensity.description" property must be truthy

Check warning on line 526 in code/API_definitions/population-density-data.yaml

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

Schema property must have a description

[S-011] Property description is missing or empty: "DensityEstimation.description" property must be truthy

Check warning on line 577 in code/Test_definitions/population-density-data.feature

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

Inconsistent Gherkin indentation

[G-002] Wrong indentation for "scenario tag", expected indentation level of 2, but got 3

Check notice on line 1 in code/API_definitions/population-density-data.yaml

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

externalDocs.description must match the DG template

[P-039] externalDocs.description in code/API_definitions/population-density-data.yaml is 'Product documentation at CAMARA.' — expected 'Product documentation at CAMARA'

Suggestion: Set externalDocs.description to exactly "Product documentation at CAMARA".

Check notice on line 183 in code/API_definitions/population-density-data.yaml

See this annotation in the file changed.

@camara-validation camara-validation / CAMARA Validation

apiRoot description should match standard text

[S-023] apiRoot description does not match the standard CAMARA text.

Check notice on line 426 in code/API_definitions/population-density-data.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 452 in code/API_definitions/population-density-data.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.