Skip to content

temporary: update if doi already taken #8

temporary: update if doi already taken

temporary: update if doi already taken #8

Triggered via release June 18, 2026 12:52
@mesemusmesemus
released v7.1.0
Status Success
Total duration 3m 47s
Artifacts 4

release.yaml

on: release
Bump, Test, and Publish the Release  /  ...  /  Extract dependencies
13s
Bump, Test, and Publish the Release / Run Tests / Extract dependencies
Bump, Test, and Publish the Release  /  ...  /  Javascript support
6s
Bump, Test, and Publish the Release / Run Tests / Javascript support
Matrix: Bump, Test, and Publish the Release / Run Tests / Tests [editable]
Matrix: Bump, Test, and Publish the Release / Run Tests / Tests [installed]
Bump, Test, and Publish the Release  /  ...  /  Lint Python
53s
Bump, Test, and Publish the Release / Run Tests / Lint Python
Matrix: Bump, Test, and Publish the Release / Run Tests / Run Javascript tests
Bump, Test, and Publish the Release  /  ...  /  Lint Javascript
Bump, Test, and Publish the Release / Run Tests / Lint Javascript
Bump, Test, and Publish the Release  /  Prepare Release
1m 8s
Bump, Test, and Publish the Release / Prepare Release
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
Bump, Test, and Publish the Release / Run Tests / Extract dependencies
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/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Bump, Test, and Publish the Release / Run Tests / Javascript support
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. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Bump, Test, and Publish the Release / Run Tests / Lint Python
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-node@v4, actions/setup-python@v5, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Bump, Test, and Publish the Release / Run Tests / Tests [installed] (3.14, 14, 24)
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-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Bump, Test, and Publish the Release / Run Tests / Tests [editable] (3.14, 14, 24)
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-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, codecov/codecov-action@v4, codecov/test-results-action@v1, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Bump, Test, and Publish the Release / Run Tests / Tests [editable] (3.14, 14, 24)
This action is being deprecated in favor of 'codecov-action'. Please update CI accordingly to use 'codecov-action@v5' with 'report_type: test_results'. The 'codecov-action' should and can be run at least once for coverage and once for test results
Bump, Test, and Publish the Release / Prepare Release
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/create-github-app-token@v2, actions/setup-python@v5, astral-sh/setup-uv@v6. 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.

Artifacts

Produced during runtime
Name Size Digest
coverage-report-3.14-14-true
121 KB
sha256:2f4d6b3fa84545f069998b8d58c6ddd920bca845c7e518ec6fc5182abcc8aaa9
requirements-3.14-14-false-false
3.17 KB
sha256:f1a491b100aa9e895fe4370cbb4780e9c114677092715a4c54dc52364cdd4f03
requirements-3.14-14-true-true
3.15 KB
sha256:aa3b3edc5312df0b78cb2fd7906d764bf51a037d68187ad01909bd9024328d3c
versions
195 Bytes
sha256:e31df591760a4533c89650da91b6674a86add69794926e7b0eaa36d71e2d52ed