Skip to main content

25.12

Β· 15 min read

[25.12] - 2025-12-03​

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 (53)​

AYaoZhan jSchuetz88 ReneSchroederLJ shijinrajbosch jalvaro-lks bosserf sm29105 Alaitz1 pjuaristi-ikerlan tfjanjua MDSBarbosa ds-asmierzchalski anneramsauer JordanGerada3 Grand-Thibault OlgaIvkovic MonikaJacobsen adkumar1 JulianSchererZF kkotowiczz hokonohara borjakhet leandro-cavalcante Akash-IAV marcelruland manourym sb3nz Usmanfee stanfaldin zygokaktus zanpi8020 th0masgl wehrstedt-jan LukasSchmetz kunyao-cofinity-x tobzahn SanaSalem01 kss682 hkny thomas-henn M-Busk Kuehner-A flarrinaga DanielaWuensch Jochen-Fischer tanvirrb dirk-qualisys sachinargade123 JSterthues jschu1 Sebastian-Wurm tobikleinfrd bilge-erdem

Committers (32)​

matbmoser CDiezRodriguez lgblaumeiser stephanbcbauer nicoprow AndrYurk SujitMBRDI typecastcloud bmg13 mgarciaLKS ClosedSourcerer ther3sa tom-rm-meyer-ISST rafaelmag110 tomaszbarwicki saadanzari agg3fe dhiren-singh-007 manojava-gk rogocof Phil91 ds-jhartmann paullatzelsperger nitin-vavdiya evegufy almadigabor mhellmeier saudkhan116 maximilianong ndr-brt ntruchsess florianrusch

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.12). 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​

info

We are excited to announce the launch of KIT 2.0 Architecture - a major redesign of how we visualize and organize our KIT ecosystem. This update brings a fresh perspective to understanding the layered architecture of Eclipse Tractus-X, making it easier than ever to explore and navigate our comprehensive collection of KITs.

For further information, please refer to the following link. If you are interested in what has changed on our website, please visit this changelog.

ComponentHelm Chart (s)App-/KIT Version (s)Release Check
Geometry KITn/a1.0.0n/a

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.
ComponentHelm Chart (s)App-/KIT Version (s)Release Check
Business Partner KITn/a11.0.0#1551
Data Driven Quality Management KITn/a2.1.0n/a
Digital Twin Registrydigital-twin-registry:0.10.00.10.0#1536
Golden Record Business Partner Number (BPN) Servicebpdm: 6.2.07.2.0#1539
Industry Core Hubindustry-core-hub:0.4.0v0.4.0#1532
Industry Core KITn/a1.5.0n/a
PURISpuris: 5.1.14.1.1#1538
Self Description (SD) Factorysdfactory: 2.1.352.1.26#1537
Tractus-X Software Development KIT (SDK)n/av0.6.1#1533

Known Knowns​

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

Industry Core Hub​

  • Complete EcoPass functionality completely included on this release (only creation of passports in a Catalog Part)
    • It will be released on a beta tag from the PR
  • One defect was found at the E2E test phase, when creating a serialized part, the "partInstanceId" field is obligatory, but if you leave it empty, it will create the part with it empty (which is not a blocker, just you will not be able to search by partInstanceId, since it is not specified): for more infomration

PURIS​

  • PURIS FOSS has not been integrated with Tractus-X Connector 0.11.x and new Policy Profile (CX25.09)
  • Rest see, Changelog, Known Knows

Tractus-X SDK​

  • Compatibility with EDC 0.11.x (Saturn) not tested completely see here

Runtime​

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

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)