25.09

[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)

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.

Highlights

note

The planned and implemented features can be found in the sig-release issue list (filtered by milestone 25.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	Helm Chart (s)	App-/KIT Version (s)	Release Check
Data Trust & Security KIT	n/a	0.0.1	#1495
Requirement KIT	n/a	0.1.0

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.
• The KITs Release Checks issues were also updated.

Component	Helm Chart (s)	App-/KIT Version (s)	Release Check
Business Partner KIT	n/a	10.0.0	#1487
BPN DID Resolution Service (BDRS)	bdrs: 0.5.7	0.5.7	#1454
Demand and Capacity Management KIT	n/a	1.4.0	#1264
Digital Twin Registry	digital-twin-registry:0.9.0	0.9.0	#1458
Tractus-X Connector (Eclipse Dataspace Components Connector)	tractusx-connector: 0.11.0	0.11.0	#1453
Golden Record Business Partner Number (BPN) Service	bpdm: 6.1.0	7.1.0	#1463
Identity and Access Management (IAM)	centralidp: 4.2.1 sharedidp: 4.2.1	keycloak: 25.0.6	#1459
Industry Core Hub	industry-core-hub:0.3.0	v0.2.0	#1456
Portal	portal: 2.6.0	registration: 2.2.2 frontend: 2.6.0 backend: 2.6.0 assets: 2.6.0	#1459
Product Carbon Footprint KIT	n/a	1.3.0
PURIS	puris: 4.1.1	3.3.0	#1448
PURIS KIT	n/a	0.4.0	#1494
Self Description (SD) Factory	sdfactory: 2.1.34	2.1.25	#1466
Supply Chain Disruption Notification KIT	n/a	2.0.0	#1480
Tractus-X Software Development KIT (SDK)	n/a	v0.5.0	#1457
Traceability KIT	n/a	7.0.0

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

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)

note

In case you have any questions about the release, please reach out to the Eclipse Tractus-X community, via Eclipse Matrix Channel and/or the Release Management room.