Skip to content

style(bundle): ruff format + drop unused imports in new v0.6.0 files #28

style(bundle): ruff format + drop unused imports in new v0.6.0 files

style(bundle): ruff format + drop unused imports in new v0.6.0 files #28

Triggered via push June 4, 2026 14:20
Status Failure
Total duration 35s
Artifacts –

release.yml

on: push
build sdist + wheel
16s
build sdist + wheel
attach artifacts to GitHub Release
8s
attach artifacts to GitHub Release
publish to PyPI (Trusted Publishing)
10s
publish to PyPI (Trusted Publishing)
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
publish to PyPI (Trusted Publishing)
Trusted publishing exchange failure: Token request failed: the server refused the request for the following reasons: * `invalid-publisher`: valid token, but no corresponding publisher (Publisher with matching claims was not found) This generally indicates a trusted publisher configuration error, but could also indicate an internal error on GitHub or PyPI's part. The claims rendered below are **for debugging purposes only**. You should **not** use them to configure a trusted publisher unless they already match your expectations. If a claim is not present in the claim set, then it is rendered as `MISSING`. * `sub`: `repo:OpenSIN-Code/SIN-Code-Bundle:environment:pypi` * `repository`: `OpenSIN-Code/SIN-Code-Bundle` * `repository_owner`: `OpenSIN-Code` * `repository_owner_id`: `280656502` * `workflow_ref`: `OpenSIN-Code/SIN-Code-Bundle/.github/workflows/release.yml@refs/tags/v0.6.0` * `job_workflow_ref`: `OpenSIN-Code/SIN-Code-Bundle/.github/workflows/release.yml@refs/tags/v0.6.0` * `ref`: `refs/tags/v0.6.0` * `environment`: `pypi` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
build sdist + wheel
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
attach artifacts to GitHub Release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, softprops/action-gh-release@v2. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
publish to PyPI (Trusted Publishing)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/