Skip to content

2.1.0

2.1.0 #13

Triggered via release July 16, 2026 08:23
@s-heppners-heppner
published 2.1.0
Status Success
Total duration 12m 20s
Artifacts 3

release.yml

on: release
sdk-publish
36s
sdk-publish
compliance-tool-publish
26s
compliance-tool-publish
server-repository-publish
12m 16s
server-repository-publish
server-discovery-publish
11m 37s
server-discovery-publish
server-registry-publish
8m 31s
server-registry-publish
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
compliance-tool-publish
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-python@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
sdk-publish
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-python@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
server-registry-publish
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, docker/build-push-action@v6, docker/metadata-action@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
server-discovery-publish
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, docker/build-push-action@v6, docker/metadata-action@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
server-repository-publish
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, docker/build-push-action@v6, docker/metadata-action@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
eclipse-basyx~basyx-python-sdk~OEW1HD.dockerbuild
190 KB
sha256:0a3790785a6822b9a909cea13bc8da098d56797be16e0d4fc0fdc9edb4e06e8e
eclipse-basyx~basyx-python-sdk~ORQQCF.dockerbuild
182 KB
sha256:50baa2bc41d7ce8f6cc106e0d9247492a3cadfeaf256f284f7c874aae93e2942
eclipse-basyx~basyx-python-sdk~XWJOSR.dockerbuild
186 KB
sha256:77594453e75e2a6a52b37b3c6864948e4490d76441799117c584e9b7824a4bed