[R24.12 [Digital Twin Registry] Release Checks

[agg3fe]

Release Info

Please provide information on what you want to be included in the Eclipse Tractus-X release. If you are not owner of this issue, please provide the information as comment to the issue. Make sure to assign this issue to expert(s) for their approval, as soon as you have finished preparation. Multiple assignees allowed; they will un-assign themselves once review completed.

Responsible contacts:

• Committer: @agg3fe , @tunacicek
• ExpertGroup: @thomas-henn , @agg3fe , @tunacicek
• Contributor contact: @agg3fe , @tunacicek

Version to be included in Eclipse Tractus-X release:

helm: digital-twin-registry-0.6.1 Image: version: 0.6.1

Leading product repository: repository link

Compliance

• [x] Possible changes (through the new features) on related Catena-X standards are considered and addressed
• [ ] Tractus-X Release Guidelines(TRGs) fulfilled https://github.com/eclipse-tractusx/sldt-digital-twin-registry/issues/480

Make sure to open and fill in a separate documentation issue in your product repository using the Quality Gate Checklist issue template

[!NOTE] Note: most criteria for documentation and security are now covered in TRGs

Functionality

• [x] Feature works as expected and described
• [x] Backward compatibility maintained (depending Major/ Minor)

Performance

• [ ] Memory and CPU usage is within acceptable limits oriented with goldilocks

Testing

• [x] Unit tests cover all new features
• [x] Integration tests are updated
• [ ] E2E/Integration test passed
• [x] Regressions tests passed

Feature summary

Please provide a list of all features that have been developed in the current phase. This list is essential for several reasons:

• Test Preparation: Identifying new features will help in the creation of new end-to-end (E2E) tests and ensure that the relevant aspects are thoroughly tested.
• Awareness: It will raise awareness of the features that need to be prioritized during the testing process.
• Board Management: This will assist in keeping the project board organized and up-to-date.

By documenting these features, you will contribute to a smoother and more efficient release process.

[!NOTE] Note: all features needs to be closed to get approval for release

Feature	Test Status	Note
Bugfix AAS3.0.2	automated APIs Done

Release Documentation

• [x] Release notes/Changelogs are updated (https://github.com/eclipse-tractusx/sldt-digital-twin-registry/blob/v0.6.1/CHANGELOG.md)
• [x] Migration scripts/documentation are included if necessary (Ensure that any database or infrastructure migrations are included).

Summary

Please provide a short summary about the new values/benefits of the new features here:

• This release includes the Bugfix- AAS 3.0.2

Helpful Links

• OpenAPI file: https://github.com/eclipse-tractusx/sldt-digital-twin-registry/blob/v0.6.1/backend/src/main/resources/static/aas-registry-openapi.yaml
• Eclipse Tractus-X openAPI specs on SwaggerHub

[tunacicek]

Ee2 Tests: No E2E Test is needed. Instead of, we tested our APIs on INT ENV successfully with our automated tests See result: https://github.com/eclipse-tractusx/sldt-digital-twin-registry/actions/runs/11775944770

[ds-hzimmer]

Test Management review: The "AAS Registry End-to-End" API test set linked above passed for version 0.6.1. Thus integration test as described in this Release Check feature + test section successful for product Digital Twin Registry. Thanks for your efforts.

Follow-up question: I am seeing on INT environment ArgoCD that "provider-dtr" in "product-semantics" namespace was updated to this latest version.

But for example https://argocd.int.catena-x.net/applications/supplier-dtr?resource= and https://argocd.int.catena-x.net/applications/customer-dtr?resource= in "product-puris" namespace as of today is still deployed with version 0.5.0 respectively 0.5.2, according to their latest implementation for release 24.08.

Assumption that those teams (PURIS, DPP, ...) should update to the new Digital Twin Registry version and then test from their side as soon as feasible, as per your latest email communication.