Changelog

The overarching project is guided by https://catena-x.net and all development work is covered in https://eclipse-tractusx.github.io.

All notable changes on the overarching level are documented in this file. Refer to component repositories for specific content, changelog and documentation.

The format is based on Keep a Changelog.

Tractus-X operates on YY.0M.MICRO Calendar Versioning for overarching, quarterly Releases. Semantic Versioning remains unchanged for all components.

[24.12] - 2024-12-02​

Implemented features can be found here

Updated​

Known Knowns​

• All not listed products and KITs have not been updated and are based on the release 24.08
  • These products were not part of the e2e testing phase
  • And are not tested with the current EDC version 0.8.0
• BPN DID Resolution Service (BDRS) is unchanged but was part of the testing phase
• PURIS is unchanged but regression tests were executed
• Knowledge Agents was updated to version 0.8.0 but only tested with the EDC release candidate 0.8.0-RC4
• This Tractus-X release does not include a Managed Identity Wallet (MIW). The development team decided on a temporary bridging solution, based on a commercial application, to test and ship Release 24.08. Without implementing this interim solution, participants will not be able to fully utilize this Tractus-X release in consequence.
• For E2E Testing, the 2.1.1 of the SSI DIM Middle Layer was used - this component is FOSS but the currently used wallet (see previous item) is not.
• Security concern about exposed technical users when subscribing BPDM services over the Portal -> see according issue
• BPNL Group Validation for a Policy does not allow a Collection as a rightOperand -> see Issue
• EDR token refresh implementation is inconsistent and deviates from the documentation -> see Issue
• Consumer-Asset with the same ID as a Provider-Asset Cannot Be Deleted After Contract Negotiation -> see Issue
• Termination of pull transfer process from consumer side does not succeed -> see Issue
• Fatal error while resume PULL transfer process -> see Issue

Runtime​

The release has been tested

• on Kubernetes versions: 1.28.9
• with PostgreSQL versions: 15.2.1.

Note: Tractus-X EDC has been tested on both Postgresql versions: 15.x and 16.x

Using helm with central helm registry​

You can search all released helm charts with the following commands:

helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versions

For installation details, please see the referenced Repositories / Releases.

[24.08] - 2024-08-05​

Added​

Updated​

Unchanged, untested​

Incompatible​

Known Knowns​

• Relevant components and interfaces developed considering Gaia-X Trust Framework - 22.10
• Connection to an external Clearing House service for the entire Catena-X ecosystem is required. The Gaia-X compliance service should generally be capable of recognizing all companies that are able to register with the Catena-X Portal.
• This Tractus-X release does not include a Managed Identity Wallet (MIW). The development team decided on a temporary bridging solution, based on a commercial application, to test and ship Release 24.08. Without implementing this interim solution, participants will not be able to fully utilize this Tractus-X release in consequence.
• For E2E Testing, the 1.2.0 of the SSI DIM Middle Layer was used - this component is FOSS but the currently used wallet (see previous item) is not.
• Documentation content (e.g. architecture, manuals etc) and folder structure have not explicitly been checked for this Release, as relevant TRGs are not yet in force. The vast majority of components are evolutions of previous Releases, with a thorough review undergone. This leads to a high confidence in the quality of existing documentation within the product repositories.
• FOSS components developed and pre-tested to TRL6 with artificial test data only
• No crosscheck of functionality in verification environment
• No execution of Load-, Performance- or Penetration Tests
• No assignment of Export Control Classification Numbers (ECCN) to FOSS components
• GeoBlocking recommended for Operations (GBaaS)
• Security concept (overall) recommended for Operations
• Listed components in "Unchanged, untested" category were not verified in combination with the current release package and are only compatible with Catena-X standards as specified. Use at your own risk at this time.
• Listed components in "Incompatible" category are not compatible with the current release package and the latest standards.
• BPDM has some Known Knowns regarding Portal integration listed in detail here
• BPDM standard configuration not compatible with Portal's Central-IDP configuration
• Portal's Partner Network page does not currently show business partner member data due to an authorization issue
• Currently not possible to add company's site and address business partners over the Portal due to authorization issue
• Security concern about exposed technical users when subscribing BPDM services over the Portal
• DTR introduces the DTR-EDC Access Control extension. The goal of this EDC extension is to enforce authorized access to submodel implementations according to AAS and Catena-X concluded contracts. It is a Maven artifact that can be used for building their own EDC dataplane image with the extension. For more details, see here.

Runtime​

The release has been tested

• on Kubernetes versions: 1.28.9
• with PostgreSQL versions: 15

Note: Tractus-X EDC has been tested on both Postgresql versions: 15.x and 16.x

Using helm with central helm registry​

You can search all released helm charts with the following commands:

helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versions

For installation details, please see the referenced Repositories / Releases.

[24.05] - 2024-05-29​

Added​

Updated​

Unchanged, untested​

Removed​

Known Knowns​

• Relevant components and interfaces developed considering Gaia-X Trust Framework - 22.10
• Connection to an external Clearing House service for the entire Catena-X ecosystem is required. The Gaia-X compliance service should generally be capable of recognizing all companies that are able to register with the Catena-X Portal. Conformity to Asset Administration Shell (AAS) API v3.0 and bugfix v3.0.1 is given. Fine granular access control introduced for optional use.
• This Tractus-X release does not include a Managed Identity Wallet (MIW). The development team decided on a temporary bridging solution, based on a commercial application, to test and ship Release 24.05. Without implementing this interim solution, participants will not be able to fully utilize this Tractus-X release in consequence. An updated and validated version of MIW is expected in Release 24.08.
• The Tractus-X EDC has undergone significant changes in its Management API, communication with external services and internal APIs.
• Documentation content (e.g. architecture, manuals etc) and folder structure have not explicitly been checked for this Release, as relevant TRGs are not yet in force. The vast majority of components are evolutions of previous Releases, with a thorough review undergone. This leads to a high confidence in the quality of existing documentation within the product repositories.
• FOSS components developed and pre-tested to TRL6 with artificial test data only
• No crosscheck of functionality in verification environment
• No execution of Load-, Performance- or Penetration Tests
• No assignment of Export Control Classification Numbers (ECCN) to FOSS components
• GeoBlocking recommended for Operations (GBaaS)
• Security concept (overall) recommended for Operations
• Listed components in "Unchanged, untested" category were not verified in combination with the current Release package and are only compatible with Catena-X Standards as specified. Use at your own risk at this time.

Runtime​

The release has been tested

• on Kubernetes versions: 1.27.3
• with PostgreSQL versions: 15

Note: Tractus-X EDC has been tested on both Postgresql versions: 15.x and 16.x

The following violations of TRG 5.07 apply:

• Golden Record Business Partner Number (BPN) Service operates on Postgresql version 16.x (not 15), but has been successfully tested for the current Release
• Country Risk deploys a Postgresql version 15 per helm chart. Yet, the test has been successfully performed on version 14.x.

Using helm with central helm registry​

You can search all released helm charts with the following commands:

helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versions

For installation details, please see the referenced Repositories / Releases.

[24.03] - 2024-03-08​

Added​

Updated​

Unchanged, untested​

Known knowns​

• Relevant components and interfaces developed considering Gaia-X Trust Framework - 22.10

• Connection to an external Clearing House service for the entire Catena-X ecosystem is required. The Gaia-X compliance service should generally be capable of recognizing all companies that are able to register with the Catena-X Portal.

• Conformity to Asset Administration Shell v3.0, API live example (AAS) is given. The DTR “/query” interface is finally deprecated and no longer available with this Release as announced. Details can be found in the changelog of the respective component.

• EDC provides no new release compared to 23.12 but only patches: EDC version 0.5.4 is part of 24.03 with the following limitations: Standard Security Tests have been performed, but it is strongly recommended for each EDC operator to apply own security measures. Especially the Dynamic Application Security Testing (DAST) needs to be executed for each specific operation environment and instance. Tractus-X release guidelines (TRGs) have been fulfilled.

• FOSS components developed and pre-tested to TRL6 with artificial test data only

• No crosscheck of functionality in verification environment

• No execution of Load-, Performance- or Penetration Tests

• No assignment of Export Control Classification Numbers (ECCN) to FOSS components

• GeoBlocking recommended for Operations (GBaaS)

• Security concept (overall) recommended for Operations

• Listed components in "Unchanged, untested" category were not verified in combination with the current Release package and are only compatible with Catena-X Standards as specified. Use at your own risk at this time.

Runtime​

• Tested on Kubernetes versions: 1.27.3

• Tested with PostgreSQL versions: 15

  • Three exceptions apply for

    • Golden Record Business Partner Number (BPN) Service
    • Managed Identity Wallet (MIW)
    • Managed Service Orchestrator (MSO)

    Those components violate TRG 5.07 as they still operate on Postgresql DB Version 14.x (not 15), but have been successfully tested for the current Release.

Using helm with central helm registry​

You can search all released helm charts with the following commands:

helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versions

For installation details, please see the referenced Repositories / Releases.

[23.12] - 2023-12-08​

Added​

Changed​

Unchanged, untested​

All components listed here have not seen any update since their previous Release. No specific regression tests executed.

Known knowns​

• Relevant components and interfaces developed considering Gaia-X Trust Framework - 22.10\ Connection to an external Clearing House service for the entire Catena-X ecosystem is required. The Gaia-X compliance service should generally be capable of recognizing all companies that are able to register with the Catena-X Portal.
• Conformity to Asset Administration Shell v3.0, API live example (AAS) is given. For compatibility reasons, the deprecated DTR query interface “/query” will additionally be supported until Q1/2024. Details can be found in the changelog of the respective component.
• EDC provides no new release compared to 23.09 but only patches: EDC version 0.5.3 is part of 23.12 with the following limitations:\ Standard Security Tests have been performed, but it is strongly recommended for each EDC operator to apply own security measures. Especially the Dynamic Application Security Testing (DAST) needs to be executed for each specific operation environment and instance.\ Tractus-X release guidelines (TRGs) 5.11, 7.01, 7.05 and 7.07 had not been fulfilled with v0.5.3. All of those are now addressed from 0.6.0-rc2 on.
• MIW interim version 0.2.0 had passed functional E2E-testing within boundaries of the Catena-X consortia, but faced severe Security issues. MIW version 0.3.0 as part of the current Release package addresses all known Security issues, but did explicitly not undergo any functional E2E-testing (again).
• FOSS components developed and pre-tested to TRL6 with artificial test data only
• No crosscheck of functionality in verification environment
• No execution of Load-, Performance- or Penetration Tests
• No assignment of Export Control Classification Numbers (ECCN) to FOSS components
• GeoBlocking recommended for Operations (GBaaS)
• Security concept (overall) recommended for Operations

Runtime​

• Tested on Kubernetes versions: 1.27.3
• Tested with PostgreSQL versions: 15

Using helm with central helm registry​

You can search all released helm charts with the following commands:

helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versions

For installation details, please see the referenced Repositories / Releases.

[23.09] - 2023-09-08​

Tractus-X has switched to YY.0M.MICRO Calendar Versioning for overarching, quarterly Releases. Therefore, the previous working title of Release 23.09 was 3.2.0. Semantic Versioning remains unchanged for all components.

Added​

Changed​

Unchanged, untested (see known knowns)​

Deprecated​

Known knowns​

• Relevant components and interfaces developed considering Gaia-X Trust Framework - 22.10\ Connection to an external Clearing House service for the entire Catena-X ecosystem is required. The Gaia-X compliance service should generally be capable of recognizing all companies that are able to register with the Catena-X Portal.
• Conformity to Asset Administration Shell v3.0, API live example (AAS) is given. For compatibility reasons, an older version of the DTR query interface “/query” will additionally be supported until the end of 2023. Details can be found in the changelog of the respective component.
• Country Risk was not verified in combination with the current Release package. Use at your own risk. The component will either be deprecated or fully re-integrated in the next Release.
• Traceability KIT was not verified in combination with the current Release package and is only compatible with Catena-X Standards as specified. Use at your own risk at this time, but expect an updated KIT version shortly.
• FOSS components developed and pre-tested to TRL6 with artificial test data only
• No crosscheck of functionality in verification environment (STABLE, Pre-PROD)
• No execution of Load-, Performance- or Penetration Tests
• No assignment of Export Control Classification Numbers (ECCN) to FOSS components
• GeoBlocking recommended for Operations (GBaaS)
• Security concept (overall) recommended for Operations

Runtime​

• Tested on Kubernetes versions: 1.25.6
• Tested with PostgreSQL versions: 15

Using helm with central helm registry​

You can search all released helm charts with the following commands:

helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versions

For installation details, please see the referenced Repositories / Releases.

[3.1.0] - 2023-05-17​

Added​

Fixed​

• n/a

Changed​

Unchanged​

Known knowns​

• Relevant components and interfaces developed considering Gaia-X Trust Framework - 22.10 Connection to an external Clearing House service for the entire Catena-X ecosystem required. The Gaia-X compliance service should generally be capable to recognize all companies that are able to register with the Catena-X Portal.
• FOSS components developed and pre-tested to TRL6 with artificial test data only
• No crosscheck of functionality in verification environment (Pre-PROD)
• No execution of Load-, Performance- or Penetration Tests
• No assignment of Export Control Classification Numbers (ECCN) to FOSS components
• GeoBlocking recommended for Operations (GBaaS)
• Security concept (overall) recommended for Operations
• Managed Identity Wallet (MIW) version 3.3.2 has passed all functional tests with the current Release package; yet this version faces a Security vulnerability with regards to libraries used (CVE-2023-0464, GHSA-fj2w-wfgv-mwq6). These issues have been addressed in MIW version 3.3.3 (no other functional changes); however MIW 3.3.3 is not part of this release.

Runtime​

• Tested on Kubernetes versions: 1.24.6
• Tested with PostgreSQL versions: 14

Using helm with central helm registry​

You can search all released helm charts with the following commands:

helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versions

For installation details, please see the referenced Repositories / Releases.

[3.0.1] - 2023-03-24​

Added​

• n/a

Fixed​

Changed​

Unchanged​

Known knowns​

• Relevant components and interfaces developed considering Gaia-X Trust Framework - 22.10 Connection to an external Clearing House service for the entire Catena-X ecosystem required. The Gaia-X compliance service should generally be capable to recognize all companies that are able to register with the Catena-X Portal.
• FOSS components developed and pre-tested to TRL6 with artificial test data only
• No crosscheck of functionality in verification environment (Pre-PROD)
• No execution of Load-, Performance- or Penetration Tests
• No assignment of Export Control Classification Numbers (ECCN) to FOSS components
• GeoBlocking recommended for Operations (GBaaS)
• Security concept (overall) recommended for Operations

Runtime​

• Tested on Kubernetes versions: 1.24.6
• Tested with PostgreSQL versions: 14

Using helm with central helm registry​

You can search all released helm charts with the following commands:

helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versions

For installation details, please see the referenced Repositories / Releases.

[3.0.0] - 2023-03-03​

Added​

• Connector KIT, v1.0.0
• Business Partner KIT, v1.0.0
• Data Chain KIT, v1.0.0
• Country Risk, Frontend v1.1.0, Backend v1.0.3
• Digital Product Pass, v0.4.6
• Trace-X Traceability Application, v1.1.0

Changed​

• Autosetup Service, Frontend v1.4.7, Backend v1.4.6
• Digital Twin Registry, v0.2.0-M3-multi-tenancy
• Dynamic Attribute Provisioning Service (DAPS), v1.7.1
• DAPS Registration Service, v1.0.5
• Eclipse Data Space Connector (EDC), v0.1.6
• Golden Record Business Partner Number (BPN) Service, v3.0.3
• Item Relationship Service (IRS), v2.3.0
• Managed Identity Wallet (MIW), v3.3.2
• Portal, v1.0.0 for Registration, Frontend, Backend and Assets
• Self Description (SD) Factory, v2.0.0
• Semantic Hub, v0.1.0-M3

Known knowns​

• Relevant components and interfaces developed considering Gaia-X Trust Framework - 22.10\ Connection to an external Clearing House service for the entire Catena-X ecosystem required.\ The Gaia-X compliance service should generally be capable to recognize all companies that are able to register with the Catena-X Portal.
• FOSS components developed and pre-tested to TRL6 with artificial test data only
• No crosscheck of functionality in verification environment (Pre-PROD)
• No execution of Load-, Performance- or Penetration Tests
• No assignment of Export Control Classification Numbers (ECCN) to FOSS components
• GeoBlocking recommended for Operations (GBaaS)
• Security concept (overall) recommended for Operations

Runtime​

• Tested on Kubernetes versions: 1.24.6
• Tested with PostgreSQL versions: 14

[2.1.0] - 2022-12-21​

Added​

• Portal, v0.6.0
• Managed Identity Wallet (MIW), v2.1.0
• Simple Data Exchanger (SDE), v1.7.0
• Autosetup Service, v1.0.1
• DAPS Registration Service, v1.0.5
• Self Description (SD) Factory, v1.0.6
• Semantic Hub, v0.1.0M1
• Item Relationship Service (IRS), v1.3.0

Known knowns​

• Developed considering Gaia-X Trust Framework - 22.04
• FOSS components developed and pre-tested to TRL6 with artificial test data only
• Restricted crosscheck of functionality in verification environment: Smoke-tests did not verify
  • Approval of company registration
  • Mutiple user onboarding
  • Registration of EDC and associated SD validations
  • IRS
• No execution of Load-, Performance- or Penetration Tests
• No assignment of Export Control Classification Numbers (ECCN) to FOSS components
• GeoBlocking recommended for Operations (GBaaS)

Runtime​

• Tested on Kubernetes versions: 1.24.3
• Tested with PostgreSQL versions: 14

[2.0.0] - 2022-12-14​

Added​

• Eclipse Data Space Connector (EDC), v0.1.2
• Golden Record Business Partner Number (BPN) Service, v2.0.0
• Dynamic Attribute Provisioning Service (DAPS), v1.7.1
• Digital Twin Registry, v0.2.0M2

Known knowns​

• FOSS components developed and pre-tested to TRL6 with artificial test data only
• No execution of Load-, Performance- or Penetration Tests
• No assignment of Export Control Classification Numbers (ECCN) to FOSS components
• GeoBlocking recommended for Operations (GBaaS)
• Portal (Registration) as well as Managed Identity Wallet scope required for full functionality; yet both are unreleased at this point in time and can be expected with Release 2.1.0
• Released Helm Chart missing for EDC v0.1.2; can be expected with Release 2.1.0

Runtime​

• Tested on Kubernetes versions: 1.24.3
• Tested with PostgreSQL versions: 14