26.09

[26.09] - 2026-09-16

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 26.09 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.

info

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 (100)

Committers (22)

info

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 our 57 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.09).

Added

KIT Name	KIT Version	Release Check
eSDScom KIT	0.0.2	n/a
PCF Data Acquisition KIT	0.0.1	n/a
Unit Process as a Service KIT	0.1.0	n/a

Updated

KIT Name	KIT Version	Release Check
Business Partner KIT	11.0.0	n/a
EcoPass KIT	1.6.0	n/a
Requirement KIT	0.1.0	#1578
Supply Chain Disruption Notification KIT	2.0.0	#1674

Known Knowns

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

Products

The planned and implemented features can be found in the sig-release issue list (filtered by milestone 26.09). 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
Tractus-X Testlab	n/a	v1-alpha3	#1729

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-Version (s)	Release Check
Digital Twin Registry	digital-twin-registry:0.13.0	0.13.0	#1676
Golden Record Business Partner Number (BPN) Service	bpdm: 7.1.0	7.5.0	#1726
Identity Hub	Holder Wallet: v0.4.1 Issuer Service: v0.4.1	Holder Wallet App: v0.4.1 Issuer Service App: v0.4.1	#1745
Item Relationship Service (IRS)	item-relationship-service: 9.1.0	7.1.0	#1673
PURIS	puris: 7.2.0	6.2.0	#1671
Tractus-X Connector (Eclipse Dataspace Components Connector)	tractusx-connector: 0.13.0	0.13.0	#1672
Tractus-X Software Development KIT (SDK)	n/a	v0.8.2	#1727

Known Knowns

• All not listed products have not been updated and are based on the release 26.06 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 26.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

Digital Twin Registry

• Migration from Bitnami to Cloudpirates pending

Golden Record Business Partner Number (BPN) Service

• Alternative headquarter remediation is mandatory before upgrading. Existing IsAlternativeHeadquarterFor relations were stored with arbitrary direction; operators must re-create them with source = alternative, target = main, and move any ownership relations and ownershipUltimate flag off alternative entities in both Pool and Gate output database.
• Site names must be unique per legal entity. A new constraint is added without resolving pre-existing duplicates — the migration fails and the deployment will not start if duplicates exist.
• Non-conforming script variants are deleted on upgrade (missing legal name, site name or physical city, or a script code the owning address does not cover). Export before upgrading if the data is needed.
• A v6 write drops a business partner's script variants, producing an UPDATE changelog entry. Mixing v6 writes with script variants is not supported.
• A script variant can no longer translate only the address; name and address of a script code are carried together, so a transliterated legal address requires a transliterated legal name.
• Ultimate owner uniqueness is evaluated against relations valid today. Future-dated ownership relations and the headquarter relocation trigger path can produce more than one ultimate owner in a tree.
• Consumers compiling against bpdm-pool-api must adjust: the affected v6 request classes lost the scriptVariants constructor parameter.

IdentityHub

• API Rest to control the custom_attestation_claims table for easier data manipulation rather than direct DB control feature will be postponed for the next release (26.12)

Item Relationship Service (IRS)

• Issue 1039
• Issue 1041
• Not compatible to >= Saturn Connector Policies
• Tested with Tractus-X Connector 0.12.2 (jupiter policy profile 24.05) and DTR 0.12.0

Tractus-X Testlab

• It is a first alpha version of the library, it may contain bugs

Runtime

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

• Kubernetes version: 1.34.1
• Applications used
  • PostgreSQL version: 15.4.0 or higher
  • DTR version 0.13.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.

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.eSDScom	1.0.0

Updated

Semantic Model Name	Model Version
io.catenax.pcf	10.0.0
io.catenax.industry_core.batch	4.0.0
io.catenax.industry_core.just_in_sequence	4.0.0
io.catenax.industry_core.serial_part	4.0.0
io.catenax.industry_core.single_level_bom_as_built	4.0.0
io.catenax.industry_core.single_level_usage_as_built	4.0.0
io.catenax.industry_core.part_type	2.0.0
io.catenax.industry_core.single_level_bom_as_planned	4.0.0
io.catenax.industry_core.single_level_usage_as_planned	3.0.0
io.catenax.shared.uuid	2.1.0
io.catenax.shared.business_partner_number	3.0.0

Deprecated

Semantic Model Name	Model Version
io.catenax.shared.uuid	1.0.0
io.catenax.shared.uuid	2.0.0
io.catenax.pcf	2.0.0
io.catenax.pcf	3.0.0
io.catenax.pcf	4.0.0
io.catenax.pcf	5.0.0
io.catenax.pcf	6.0.0
io.catenax.pcf	7.0.0
io.catenax.pcf	8.0.0
io.catenax.batch	1.0.2
io.catenax.batch	2.0.0
io.catenax.batch	3.0.0
io.catenax.batch	3.0.1
io.catenax.batch	3.0.0
io.catenax.batch	4.0.0
io.catenax.just_in_sequence	1.0.0
io.catenax.just_in_sequence	2.0.0
io.catenax.just_in_sequence	3.0.0
io.catenax.just_in_sequence	4.0.0
io.catenax.serial_part	1.0.1
io.catenax.serial_part	2.0.0
io.catenax.serial_part	4.0.0
io.catenax.single_level_bom_as_built	1.0.0
io.catenax.single_level_bom_as_built	2.0.0
io.catenax.single_level_bom_as_built	3.0.0
io.catenax.single_level_bom_as_built	4.0.0
io.catenax.single_level_usage_as_built	1.0.0
io.catenax.single_level_usage_as_built	2.0.0
io.catenax.single_level_usage_as_built	3.0.0
io.catenax.single_level_usage_as_built	4.0.0
io.catenax.part_type_information	1.0.0
io.catenax.part_type_information	2.0.0
io.catenax.single_level_bom_as_planned	2.0.0
io.catenax.single_level_bom_as_planned	3.0.0
io.catenax.single_level_bom_as_planned	4.0.0
io.catenax.single_level_usage_as_planned	1.1.0
io.catenax.single_level_usage_as_planned	2.0.0
io.catenax.single_level_usage_as_planned	3.0.0
io.catenax.shared.business_partner_number	1.0.0
io.catenax.shared.business_partner_number	2.0.0