Skip to content

v1.27.1

v1.27.1 #73

Triggered via release May 8, 2026 16:45
@maxisbeymaxisbey
published v1.27.1
Status Success
Total duration 5m 43s
Artifacts 1

publish-pypi.yml

on: release
Matrix: checks / test
checks  /  pre-commit
52s
checks / pre-commit
checks  /  doc-snippets
12s
checks / doc-snippets
Build distribution
9s
Build distribution
Upload release to PyPI
24s
Upload release to PyPI
docs-publish
25s
docs-publish
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
maxisbey
approved May 8, 2026
release

Annotations

23 warnings and 9 notices
checks / doc-snippets
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.12.3-pruned-6b4d0995aa85cf7736a93bb2e09de49090752f0e769c7e55599ba10c7367d5da, another job may be creating this cache.
checks / test (3.10, lowest-direct, ubuntu-latest)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.12.3-pruned-6b4d0995aa85cf7736a93bb2e09de49090752f0e769c7e55599ba10c7367d5da, another job may be creating this cache.
checks / test (3.10, highest, ubuntu-latest)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.12.3-pruned-6b4d0995aa85cf7736a93bb2e09de49090752f0e769c7e55599ba10c7367d5da, another job may be creating this cache.
checks / test (3.11, lowest-direct, ubuntu-latest)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.12.3-pruned-6b4d0995aa85cf7736a93bb2e09de49090752f0e769c7e55599ba10c7367d5da, another job may be creating this cache.
checks / test (3.12, highest, ubuntu-latest)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.12.3-pruned-6b4d0995aa85cf7736a93bb2e09de49090752f0e769c7e55599ba10c7367d5da, another job may be creating this cache.
checks / test (3.11, highest, ubuntu-latest)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.12.3-pruned-6b4d0995aa85cf7736a93bb2e09de49090752f0e769c7e55599ba10c7367d5da, another job may be creating this cache.
checks / test (3.13, highest, ubuntu-latest)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.12.3-pruned-6b4d0995aa85cf7736a93bb2e09de49090752f0e769c7e55599ba10c7367d5da, another job may be creating this cache.
checks / test (3.12, lowest-direct, ubuntu-latest)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.12.3-pruned-6b4d0995aa85cf7736a93bb2e09de49090752f0e769c7e55599ba10c7367d5da, another job may be creating this cache.
checks / pre-commit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
checks / test (3.11, lowest-direct, windows-latest)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-pc-windows-msvc-windows-2025-3.12.10-pruned-b27fbfac144336fe3de5e2a29b0abfce6eeb0efef9f78731b27d1746fbf9cc71, another job may be creating this cache.
checks / test (3.10, lowest-direct, windows-latest)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-pc-windows-msvc-windows-2025-3.12.10-pruned-b27fbfac144336fe3de5e2a29b0abfce6eeb0efef9f78731b27d1746fbf9cc71, another job may be creating this cache.
checks / test (3.13, highest, windows-latest)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-pc-windows-msvc-windows-2025-3.12.10-pruned-b27fbfac144336fe3de5e2a29b0abfce6eeb0efef9f78731b27d1746fbf9cc71, another job may be creating this cache.
checks / test (3.13, lowest-direct, windows-latest)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-pc-windows-msvc-windows-2025-3.12.10-pruned-b27fbfac144336fe3de5e2a29b0abfce6eeb0efef9f78731b27d1746fbf9cc71, another job may be creating this cache.
checks / test (3.12, highest, windows-latest)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-pc-windows-msvc-windows-2025-3.12.10-pruned-b27fbfac144336fe3de5e2a29b0abfce6eeb0efef9f78731b27d1746fbf9cc71, another job may be creating this cache.
checks / test (3.11, highest, windows-latest)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-pc-windows-msvc-windows-2025-3.12.10-pruned-b27fbfac144336fe3de5e2a29b0abfce6eeb0efef9f78731b27d1746fbf9cc71, another job may be creating this cache.
checks / test (3.12, lowest-direct, windows-latest)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-pc-windows-msvc-windows-2025-3.12.10-pruned-b27fbfac144336fe3de5e2a29b0abfce6eeb0efef9f78731b27d1746fbf9cc71, another job may be creating this cache.
Build distribution
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/upload-artifact@v4, astral-sh/setup-uv@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build distribution
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0zBP+aQAAAABE4hqw07HVTJfyy06KDIPpUEhMMzBFREdFMDQxMgBFZGdl
Build distribution
Failed to restore: Cache service responded with 400
Upload release to PyPI
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 2nd, 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/
docs-publish
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, astral-sh/setup-uv@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
docs-publish
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0YBT+aQAAAADx8Qt3cvYaQLfZKLvLAUjMUEhYMzFFREdFMDUxMwBFZGdl
docs-publish
Failed to restore: Cache service responded with 400
checks / test (3.10, highest, windows-latest)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
checks / test (3.11, lowest-direct, windows-latest)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
checks / test (3.10, lowest-direct, windows-latest)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
checks / test (3.13, highest, windows-latest)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
checks / test (3.13, lowest-direct, windows-latest)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
checks / test (3.12, highest, windows-latest)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
checks / test (3.11, highest, windows-latest)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
checks / test (3.12, lowest-direct, windows-latest)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Upload release to PyPI
Generating and uploading digital attestations

Artifacts

Produced during runtime
Name Size Digest
release-dists
796 KB
sha256:55f801f7ccab112cf8bf6cd69851734348fd42eaf25fb5a530259b07efa83338