26.03

[26.03] - 2026-03-18

The success of Tractus-X and each of our releases is driven by the strength and dedication of our community. We would like to thank everyone who contributed to making the 25.03 release possible.

Whether by reporting issues, engaging in constructive discussions, proposing solutions, writing code, reviewing pull requests, improving documentation, or supporting others in the community, every contribution plays an important role in moving the project forward.

Open collaboration is at the heart of Tractus-X, and this release once again demonstrates what can be achieved.
Your expertise, commitment, and willingness to collaborate are what make continuous innovation possible.

Note

Thank You for your ongoing support and contributions.

We are looking forward to continuing this journey together with the community and to building the next releases of Tractus-X.

Contributors (151)

Committers (27)

Note

The above list contains all contributors and committers that have been involved in this release. The list is generated automatically based on the amount of contributions to the repositories
of the Eclipse Tractus-X organization on GitHub.

It's not only about code contributions, but also about reporting issues, discussing solutions, writing documentation, or reviewing contributions.

KITs

Our KITs are continuously evolving, with new additions and updates happening. The planned KITs can be found in the sig-release issue list (filtered by milestone 26.03).

Added

KIT Name	KIT Version	Release Check
AI Service KIT	0.0.1	#1574
CBAM KIT	0.1.0	#1625
Company Certificate Management KIT	0.1.0	n/a
Due Diligence Check KIT	0.0.1	#1624
Engineering as a Service (EaaS) KIT	0.0.1	#1552
Modular Engineering (ModEng) KIT	0.0.1	#1562

Updated

KIT Name	KIT Version	Release Check
Connector KIT	4.0.0	#1582
Digital Twin KIT	2.0.2	#1560
EcoPass KIT	1.5.1	#1579
PURIS KIT	0.4.1	#1591
Traceability KIT	8.0.0	n/a

Known Knowns

• All not listed KITs have not been updated and are based on the release 25.12 or previous releases

Products

The planned and implemented features can be found in the sig-release issue list (filtered by milestone 26.03). These features describe only the requested new function/functionality.
Most of the features are linked to product specific issues. Please have a look on product specific repositories for detailed information on the product specific issues tabs.

Added

Component Name	Helm Chart (s)	App Version (s)	Release Check
Identity Hub	Holder Wallet: v0.2.0 Issuer Service: v0.2.0	Holder Wallet App: v0.2.0 Issuer Service App: v0.2.0	#1584

Updated

Note

• The product Release Checks issues for each product have been updated to reflect the new versions of the components included in this release. Please refer to these issues for detailed information on the updates.

Component Name	Helm Chart (s)	App-/KIT-/ Model- Version (s)	Release Check
Digital Twin Registry	digital-twin-registry:0.11.0	0.11.0	#1594
Golden Record Business Partner Number (BPN) Service	bpdm: 6.3.0	7.3.0	#1592
Industry Core Hub	industry-core-hub:0.5.0	v0.5.0	#1583
Tractus-X Software Development KIT (SDK)	n/a	v0.7.1	#1585
Tractus-X Connector (Eclipse Dataspace Components Connector)	tractusx-connector: 0.12.0	0.12.0	#1580

Known Knowns

• All not listed products and KITs have not been updated and are based on the release 25.12 or previous releases
  • 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, 25.09 and 25.12. 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

• Due to last minute vulnerabilties, E2E tests were not executed on the latest code state (#1620 was not covered by E2E tests)
• Due to vulnerabilties present in the base layer, the BPDM images offered in Dockerhub currently contain vulnerabilities

Identity Hub

• The identity hub wallet was not tested with a Tractus-X EDC Connector yet (planned for R26.06) to be fully functional
• The issuer service is not integrated with the portal backend (because of a limitation from the portal for the bring your own wallet topic)
• The wallet currently supports only one issuer (is configuration issue)
• Currently there is not possible to issue the membership credential as defined in the CX-0050 standard from Catena-X, because of a missing feature in upstream: Possible BUG: JWT credential @context is hardcoded and not configurable via CredentialDefinition API
  • Custom Contexts are not allowed, so the "memberOf" key is not possible to be included.

Industry Core Hub

• The notification api is not working for saturn because of a Bug: Backend notifications API is not compatible with Saturn connector. industry-core-hub#529 (which can not be fixed until the end of the release, however is a additional feature)
• Notifications can't be sent via frontend. Currently this is not implemented.
• Digital Product Passport consumption can fail if policy configuration was not made correctly in the connector.

Runtime

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

• Kubernetes version: 1.33.1
• Applications used
  • PostgreSQL version: 15.4.0 or higher
  • DTR version 0.10.0

Note

Tractus-X Connector 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

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.

Tip

If you are using a provided helm chart from Eclipse Tractus-X that uses Bitnami container images and it doesn't work, please check the values.yaml file of the respective chart
and update/overwrite the image repository from bitnami/<image-name> to bitnamilegacy/<image-name>.

Extract from values.yaml:

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

Tip

For installation details, please see the referenced Repositories / Releases and related documentation (e.g. migration documentation)

Semantic Models

Added

Semantic Model Name	Model Version
io.catenax.batch	4.0.0
io.catenax.material_accounting	1.0.0
io.catenax.pcf_for_battery_component_supplier	1.0.0
io.catenax.sbom	1.0.0
io.catenax.shared.standard_codes	1.0.0
io.catenax.shared.material_classification	1.0.0
io.catenax.shared.industry_core.common	1.0.0
io.catenax.shared.industry_core.manufacturing_information	1.0.0
io.catenax.shared.industry_core.site_information	1.0.0

Updated

Semantic Model Name	Model Version
io.catenax.just_in_sequence_part	4.0.0
io.catenax.part_type_information	2.0.0
io.catenax.serial_part	4.0.0
io.catenax.single_level_bom_as_built	4.0.0
io.catenax.single_level_bom_as_planned	4.0.0
io.catenax.single_level_usage_as_built	4.0.0
io.catenax.generic.digital_product_passport	7.0.0
io.catenax.us_tariff_information	2.0.0
io.catenax.single_level_usage_as_planned	3.0.0
io.catenax.quantity	3.0.0

Deprecated

Semantic Model Name	Model Version
io.catenax.single_level_usage_as_planned	1.0.0
io.catenax.shared.part_classification	1.0.0
io.catenax.shared.part_site_information	1.0.0
io.catenax.shared.part_site_information	2.0.0
io.catenax.shared.quantity	1.0.0

Known Knowns

• All not listed semantic models have not been updated and are based on the release 25.12 or previous releases