14 posts tagged with "release"

[25.09] - 2025-10-01​

Our community and results/releases depends on our contributors. We want to thank everyone who has contributed to this release by reporting issues, discussing solutions, writing code, or reviewing contributions.

Contributors (62)​

Committers (34)​

Highlights​

Added​

Updated​

Known Knowns​

• All not listed products and KITs have not been updated and are based on the release 25.06
  • These products were not part of the testing phase
• The Eclipse Tractus-X release does not include an Identity Wallet. The development team decided on a temporary bridging solution, based on a commercial application, to test and ship the releases 24.08, 24.12, 25.03, 25.06 and 25.09. Without implementing this interim solution, participants will not be able to fully utilize this release in consequence.
• For E2E Testing, the 2.2.3 of the SSI DIM Middle Layer was used - this component is FOSS but the currently used wallet (see previous item) is not

BPDM​

• When creating a marketplace app the Portal does not support an internal technical user profile for BPDM permission group Gate Input Consumer. Therefore, it is currently not possible to create a marketplace app that enables access to ReadAccessGateInputForSharingMember offers for external VAT services wanting to access sharing member Gates
• For the new Tractus-X Connector 0.11 the golden record process was only tested on the 3rd release candidate, not the actual released version. There were no backwards compatibility tests between older Tractus-X Connector versions and the new Tractus-X Connector 0.11.
• BPDM currently only offers documentation on how to use the Tractus-X Connector 0.11 over DCP 1.0. There are no tutorials for DCP 0.8 available.

Tractus-X Connector​

• Beware of the changes in the acceptable policies, which inflict breaking changes required by services that create new policies -- see migration guide for more information.
• Policy right operands given as array are not returned as specified, they work, but the returned right operand is a string representation of the json object(#2221)
• DCP implementation uses a wrong property name. SAP DIM is capable to deal with the wrong property name (#2255)
• Application of policies that can be ensured automatically not complete (#2259)
• There is a complex issue about the compatibility of policies with dsp versions, especially regarding backward compatibility (#2288). The issue requires further investigation which we will execute to separate misbehavior from documentation issues.

Industry Core Hub​

• RLock is blocking other API calls when negotiation is not successful at the Discovery: industry-core-hub#334
• Trivy scan fails to complete successfully because of alpine version: industry-core-hub#319
• When the Tractus-X Connector restarts, the Connector assets are not recreated for the already available twins: industry-core-hub#318
• Incompatible with Tractus-X Connector 0.11.x: (additional)
  • Not compliant to CX-0018, due to NOT evaluating the dspace endpoint.
  • Not compliant to CX-0152, due to NOT implementing the new odrl profile.
• No authentication is implemented (it will be included in R25.12, PR is ready): industry-core-hub#254

PURIS​

• Data Assets and DTR not covered in migrations
• Data Sovereignty is not transparent to end-users
• Catalog and Negotiations have bad user experience (no actions, no filters)
• Incompatible with Tractus-X Connector 0.11.x: (additional)
  • Not tested with Tractus-X Connector in version 0.11.x
  • Not compliant to CX-0018, due to NOT evaluating the dspace endpoint.
  • Not compliant to CX-0152, due to NOT implementing the new odrl profile.

Tractus-X SDK​

• Compatibility with Tractus-X Connector 0.11.x (Saturn) not tested completely: tractusx-sdk#159
  • The Saturn APIs were implemented but were not able to be tested because of different bugs found at the connector and due to missing documentation on how to adopt it.

Runtime​

The following runtime has been used during end-to-end test:

• Kubernetes version: 1.29.10
• Applications used
  • PostgreSQL version: 15.4.0 or more specifically 15.4.0-debian-11-r45
  • Tractus-X Connector version 0.11.0
  • DTR version 0.9.0

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

Bitnami changes​

The official Bitnami Helm chart repository has been deprecated or is no longer maintained in its previous location. Bitnami has migrated legacy container images to a new repository called bitnamilegacy. Helm charts using Bitnami container images must be updated to reference this new source to ensure continued functionality. With bitnamilegacy we won’t receive security updates.

Extract from values.yaml:

postgresql:
  image:
    # -- workaround to use bitnamilegacy chart
    repository: bitnamilegacy/postgresql
    tag: 15.4.0-debian-11-r45

[25.06] - 2025-06-16​

Implemented features can be found here

Added​

Updated​

Known Knowns​

• All not listed products and KITs have not been updated and are based on the release 25.03
  • These products were not part of the e2e testing phase
  • And are not tested with the current EDC version 0.10.0 and the current DTR version 0.8.0
• The Eclipse Tractus-X release does not include an Identity Wallet. The development team decided on a temporary bridging solution, based on a commercial application, to test and ship the releases 24.08, 24.12, 25.03 and 25.06. Without implementing this interim solution, participants will not be able to fully utilize this release in consequence.
• For E2E Testing, the 2.2.3 of the SSI DIM Middle Layer was used - this component is FOSS but the currently used wallet (see previous item) is not

BPDM​

• When creating a marketplace app the Portal does not support an internal technical user profile for BPDM permission group Gate Input Consumer. Therefore, it is currently not possible to create a marketplace app that enables access to ReadAccessGateInputForSharingMember offers for external VAT services wanting to access sharing member Gates

Industry Core Hub​

• No Authentication at the backend & frontend provided see here
• No profile & settings provided at frontend (just a mock) see here
• Part Instance twins not included in scope (not supported in backend, and mocked in the frontend) see here
• Not submodel is displayed in the frontend, also is not possible to create submodels see here
• No display of aspect models in frontend. (PCF and other data models are not supported, just PartTypeInformation v1.0.0) see here
• It is not possible to unshare once shared see here

Item Relationship Service (IRS)​

• Persistent submodel service needed for end-to-end stability see here

Portal​

Backend​

• Connector URL: Updating connector URL for connectors with missing SD Document is not working see here
• for comprehensive list see here

Frontend​

• Auto-setup feature for App Subscriptions: validation is triggered on opening pop up see here
• for comprehensive list see here

Software Development KIT​

• EDC Version specified is v0_9_0 but works with v0.10.0 see here
• EDC Service has not factory method. see here

Trace-X Traceability Application​

• The "Show Details Table" function is non-functional in the as Planned view see here
• Record Information is Visible for asPlanned Parts to Users with Supervisor Role (only role Admin shold be permitted) see here
• Insufficient visualization of Teaction Battery Code see here

Runtime​

The following runtime has been used during end-to-end test:

• Kubernetes version: 1.29.10
• PostgreSQL version: 15.4.0 or more specifically 15.4.0-debian-11-r45
• EDC version 0.10.0
• DTR version 0.8.0

[25.03] - 2025-03-19​

Implemented features can be found here

Added​

Updated​

Removed / Deprecated​

Known Knowns​

• All not listed products and KITs have not been updated and are based on the release 24.12
  • These products were not part of the e2e testing phase
  • And are not tested with the current EDC version 0.9.0
• The Eclipse Tractus-X release does not include an Identity Wallet. The development team decided on a temporary bridging solution, based on a commercial application, to test and ship the releases 24.08, 24.12 and 25.03. Without implementing this interim solution, participants will not be able to fully utilize this release in consequence.
• For E2E Testing, the 2.2.1 of the SSI DIM Middle Layer was used - this component is FOSS but the currently used wallet (see previous item) is not.
• 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

EDC​

• Any EDC will not work with a Hashicorp Vault version 1.18.1 as this version has a bug, incompatibilities to other versions are not known.
• Compared with the catalog from version 0.7.7, the "endpointUrl" property in a Dataset is always in namespace "dcat", a redundant property in namespace "dct" is not available anymore.

BDRS​

• BDRS will not work with a Hashicorp Vault version 1.18.1 as this version has a bug, incompatibilities to other versions are not known.

Digital Product Pass​

• Digital Product Pass (DPP) will be not part of the release

Knowledge Agents​

• Knowledge Agents is not part of this release but was tested with the EDC release candidate 0.8.0-RC4

Portal​

• Note for Gaia-X Clearing House Tagus upgrade (Portal v2.4.0, Eclipse Tractus-X R25.03):
  • If a company was onboarded with ELBE clearing house, the legal person self description document is not accepted when creating a connector with newer versions of the clearing house. Portal operators are advised to create new legal person and connector self description documents for all previously onboarded companies.
  • As of v2.4.0, the portal backend will activate connector without updated legal person self description document to allow for a transition phase. The connector will not have a document until reissuance for both company and connector is triggered by operators.
  • An automatic reissuance system is planned for the future.
• When registering two connectors (EDCs) under one technical user, the technical user will be duplicated and the details of the technical user will not be shown

Runtime​

• on Kubernetes versions: 1.29.10
• with PostgreSQL versions: 15.4.0. or more specific 15.4.0-debian-11-r45
• the EDC version 0.9.0-rc2 was used for testing

[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

[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

[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

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

[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

[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

[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

[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