Skip to content

Fix: opsplanning is not timezone aware #53

Fix: opsplanning is not timezone aware

Fix: opsplanning is not timezone aware #53

Triggered via push June 29, 2026 14:39
Status Failure
Total duration 30s
Artifacts 1
Build distribution 📦
13s
Build distribution 📦
Sign the Resourcecode 📦 with Sigstore and upload them to GitHub Release
0s
Sign the Resourcecode 📦 with Sigstore and upload them to GitHub Release
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
Publish Resourcecode 📦 to TestPyPI
Process completed with exit code 2.
Build distribution 📦
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Publish Resourcecode 📦 to TestPyPI
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/download-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Publish Resourcecode 📦 to TestPyPI
No file matched to [/home/runner/work/py-resourcecode/py-resourcecode/**/*requirements*.txt,/home/runner/work/py-resourcecode/py-resourcecode/**/*requirements*.in,/home/runner/work/py-resourcecode/py-resourcecode/**/*constraints*.txt,/home/runner/work/py-resourcecode/py-resourcecode/**/*constraints*.in,/home/runner/work/py-resourcecode/py-resourcecode/**/pyproject.toml,/home/runner/work/py-resourcecode/py-resourcecode/**/uv.lock,/home/runner/work/py-resourcecode/py-resourcecode/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.

Artifacts

Produced during runtime
Name Size Digest
resourcecode
21.5 MB
sha256:8a8e73f65b6bea1eae33691613b80e0c7ea0c96ee5d6053f4b2df1bd4c3f0fc2