Skip to content
CI

CI #25

Sign in to view logs

CI

CI #25

Manually triggered September 26, 2025 20:29
@bkeryanbkeryan
⁠ ca06ea1
users/bkeryan/fix-setup-poetry-dir
Status Cancelled
Total duration 1m 50s
Artifacts –

CI.yml

on: workflow_dispatch
Matrix: Test actions / Test setup-poetry
Matrix: Test actions / Test analyze-project
Matrix: Test actions / Test analyze-project in root of repo
Matrix: Test actions / Test setup-python
Test actions  /  Test check-project-version
17s
Test actions / Test check-project-version
Test actions  /  Test update-project-version
23s
Test actions / Test update-project-version
Matrix: Test actions / Test setup-poetry (cache hit)
Matrix: Test actions / Test setup-poetry (no cache)
Test actions  /  Test Results
0s
Test actions / Test Results
Fit to window
Zoom out
Zoom in

Annotations

121 errors and 44 notices
Test actions / Test check-project-version
Process completed with exit code 1.
Project Version Error
The project version in pyproject.toml does not match the expected version. If this workflow was triggered by a GitHub release, verify that the release was tagged with the correct version. If they don't match, you should either update pyproject.toml or delete and re-create the release with the correct tag. Project version: 1.0.0 Expected version: 1.0.1
Test actions / Test analyze-project in root of repo (windows-latest, 3.11)
Process completed with exit code 1.
Test actions / Test analyze-project in root of repo (windows-latest, 3.9)
Process completed with exit code 1.
Test actions / Test analyze-project in root of repo (windows-latest, 3.9)
The strategy configuration was canceled because "test_actions.test_analyze_project_in_root.windows-latest_3_11" failed
Test actions / Test analyze-project in root of repo (macos-latest, 3.9)
The operation was canceled.
Test actions / Test analyze-project in root of repo (macos-latest, 3.9)
The strategy configuration was canceled because "test_actions.test_analyze_project_in_root.windows-latest_3_11" failed
Test actions / Test analyze-project in root of repo (ubuntu-latest, pypy3.10)
The operation was canceled.
Test actions / Test analyze-project in root of repo (ubuntu-latest, pypy3.10)
The strategy configuration was canceled because "test_actions.test_analyze_project_in_root.windows-latest_3_11" failed
Test actions / Test analyze-project in root of repo (windows-latest, 3.13)
The operation was canceled.
Test actions / Test analyze-project in root of repo (windows-latest, 3.13)
The strategy configuration was canceled because "test_actions.test_analyze_project_in_root.windows-latest_3_11" failed
Test actions / Test analyze-project in root of repo (macos-latest, pypy3.11)
The operation was canceled.
Test actions / Test analyze-project in root of repo (macos-latest, pypy3.11)
The strategy configuration was canceled because "test_actions.test_analyze_project_in_root.windows-latest_3_11" failed
Test actions / Test analyze-project in root of repo (windows-latest, pypy3.11)
The operation was canceled.
Test actions / Test analyze-project in root of repo (windows-latest, pypy3.11)
The strategy configuration was canceled because "test_actions.test_analyze_project_in_root.windows-latest_3_11" failed
Test actions / Test analyze-project in root of repo (macos-latest, pypy3.10)
The operation was canceled.
Test actions / Test analyze-project in root of repo (macos-latest, pypy3.10)
The strategy configuration was canceled because "test_actions.test_analyze_project_in_root.windows-latest_3_11" failed
Test actions / Test analyze-project in root of repo (windows-latest, pypy3.10)
The operation was canceled.
Test actions / Test analyze-project in root of repo (windows-latest, pypy3.10)
The strategy configuration was canceled because "test_actions.test_analyze_project_in_root.windows-latest_3_11" failed
Test actions / Test analyze-project in root of repo (windows-latest, 3.12)
The operation was canceled.
Test actions / Test analyze-project in root of repo (windows-latest, 3.12)
The strategy configuration was canceled because "test_actions.test_analyze_project_in_root.windows-latest_3_11" failed
Test actions / Test analyze-project in root of repo (windows-latest, 3.10)
The operation was canceled.
Test actions / Test analyze-project in root of repo (windows-latest, 3.10)
The strategy configuration was canceled because "test_actions.test_analyze_project_in_root.windows-latest_3_11" failed
Test actions / Test analyze-project in root of repo (ubuntu-latest, 3.10)
The operation was canceled.
Test actions / Test analyze-project in root of repo (ubuntu-latest, 3.10)
The strategy configuration was canceled because "test_actions.test_analyze_project_in_root.windows-latest_3_11" failed
Test actions / Test analyze-project in root of repo (ubuntu-latest, 3.9)
The operation was canceled.
Test actions / Test analyze-project in root of repo (ubuntu-latest, 3.9)
The strategy configuration was canceled because "test_actions.test_analyze_project_in_root.windows-latest_3_11" failed
Test actions / Test analyze-project in root of repo (ubuntu-latest, 3.13)
The operation was canceled.
Test actions / Test analyze-project in root of repo (ubuntu-latest, 3.13)
The strategy configuration was canceled because "test_actions.test_analyze_project_in_root.windows-latest_3_11" failed
Test actions / Test analyze-project in root of repo (ubuntu-latest, 3.11)
The operation was canceled.
Test actions / Test analyze-project in root of repo (ubuntu-latest, 3.11)
The strategy configuration was canceled because "test_actions.test_analyze_project_in_root.windows-latest_3_11" failed
Test actions / Test analyze-project in root of repo (macos-latest, 3.12)
The operation was canceled.
Test actions / Test analyze-project in root of repo (macos-latest, 3.12)
The strategy configuration was canceled because "test_actions.test_analyze_project_in_root.windows-latest_3_11" failed
Test actions / Test analyze-project in root of repo (ubuntu-latest, pypy3.11)
The operation was canceled.
Test actions / Test analyze-project in root of repo (ubuntu-latest, pypy3.11)
The strategy configuration was canceled because "test_actions.test_analyze_project_in_root.windows-latest_3_11" failed
Test actions / Test analyze-project in root of repo (macos-latest, 3.10)
The operation was canceled.
Test actions / Test analyze-project in root of repo (macos-latest, 3.10)
The strategy configuration was canceled because "test_actions.test_analyze_project_in_root.windows-latest_3_11" failed
Test actions / Test analyze-project in root of repo (ubuntu-latest, 3.12)
The operation was canceled.
Test actions / Test analyze-project in root of repo (ubuntu-latest, 3.12)
The strategy configuration was canceled because "test_actions.test_analyze_project_in_root.windows-latest_3_11" failed
Test actions / Test analyze-project in root of repo (macos-latest, 3.11)
The operation was canceled.
Test actions / Test analyze-project in root of repo (macos-latest, 3.11)
The strategy configuration was canceled because "test_actions.test_analyze_project_in_root.windows-latest_3_11" failed
Test actions / Test analyze-project in root of repo (macos-latest, 3.13)
The operation was canceled.
Test actions / Test analyze-project in root of repo (macos-latest, 3.13)
The strategy configuration was canceled because "test_actions.test_analyze_project_in_root.windows-latest_3_11" failed
Test actions / Test setup-poetry (cache hit) (windows-latest, 3.11)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (cache hit) (ubuntu-latest, 3.13)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (cache hit) (ubuntu-latest, pypy3.10)
The operation was canceled.
Test actions / Test setup-poetry (cache hit) (ubuntu-latest, pypy3.10)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (cache hit) (macos-latest, 3.11)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (cache hit) (ubuntu-latest, 3.10)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (macos-latest, 3.9)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (macos-latest, 3.9)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (macos-latest, pypy3.11)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (macos-latest, pypy3.11)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (macos-latest, pypy3.10)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (macos-latest, pypy3.10)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (cache hit) (macos-latest, pypy3.10)
The operation was canceled.
Test actions / Test setup-poetry (cache hit) (macos-latest, pypy3.10)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (cache hit) (macos-latest, 3.10)
The operation was canceled.
Test actions / Test setup-poetry (cache hit) (macos-latest, 3.10)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (macos-latest, 3.10)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (macos-latest, 3.10)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (cache hit) (macos-latest, pypy3.11)
The operation was canceled.
Test actions / Test setup-poetry (cache hit) (macos-latest, pypy3.11)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (cache hit) (macos-latest, 3.9)
The operation was canceled.
Test actions / Test setup-poetry (cache hit) (macos-latest, 3.9)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (cache hit) (windows-latest, 3.12)
The operation was canceled.
Test actions / Test setup-poetry (cache hit) (windows-latest, 3.12)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (macos-latest, 3.13)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (macos-latest, 3.13)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (cache hit) (ubuntu-latest, pypy3.11)
The operation was canceled.
Test actions / Test setup-poetry (cache hit) (ubuntu-latest, pypy3.11)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (ubuntu-latest, 3.12)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (ubuntu-latest, 3.12)
The run was canceled by @bkeryan.
Test actions / Test analyze-project (windows-latest, pypy3.10)
The operation was canceled.
Test actions / Test analyze-project (windows-latest, pypy3.10)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (ubuntu-latest, 3.13)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (ubuntu-latest, 3.13)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (windows-latest, 3.9)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (windows-latest, 3.9)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (windows-latest, 3.12)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (windows-latest, 3.12)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (cache hit) (windows-latest, 3.13)
The operation was canceled.
Test actions / Test setup-poetry (cache hit) (windows-latest, 3.13)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (ubuntu-latest, 3.9)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (ubuntu-latest, 3.9)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (windows-latest, 3.11)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (windows-latest, 3.11)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (cache hit) (windows-latest, pypy3.11)
The operation was canceled.
Test actions / Test setup-poetry (cache hit) (windows-latest, pypy3.11)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (windows-latest, 3.13)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (windows-latest, 3.13)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (cache hit) (windows-latest, pypy3.10)
The operation was canceled.
Test actions / Test setup-poetry (cache hit) (windows-latest, pypy3.10)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (macos-latest, 3.12)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (macos-latest, 3.11)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (macos-latest, 3.12)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (macos-latest, 3.11)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (windows-latest, pypy3.11)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (windows-latest, pypy3.11)
The run was canceled by @bkeryan.
Test actions / Test analyze-project (windows-latest, 3.9)
The operation was canceled.
Test actions / Test analyze-project (windows-latest, 3.9)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (windows-latest, 3.10)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (windows-latest, 3.10)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (cache hit) (windows-latest, 3.9)
The operation was canceled.
Test actions / Test setup-poetry (cache hit) (windows-latest, 3.9)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (windows-latest, pypy3.10)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (windows-latest, pypy3.10)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (ubuntu-latest, 3.11)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (ubuntu-latest, 3.11)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (ubuntu-latest, 3.10)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (ubuntu-latest, 3.10)
The run was canceled by @bkeryan.
Test actions / Test analyze-project (windows-latest, pypy3.11)
The operation was canceled.
Test actions / Test analyze-project (windows-latest, pypy3.11)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (cache hit) (windows-latest, 3.10)
The operation was canceled.
Test actions / Test setup-poetry (cache hit) (windows-latest, 3.10)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (ubuntu-latest, pypy3.11)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (ubuntu-latest, pypy3.11)
The run was canceled by @bkeryan.
Test actions / Test setup-poetry (no cache) (ubuntu-latest, pypy3.10)
The operation was canceled.
Test actions / Test setup-poetry (no cache) (ubuntu-latest, pypy3.10)
The run was canceled by @bkeryan.
CI
The run was canceled by @bkeryan.
CI
The run was canceled by @bkeryan.
Test actions / Test setup-python (windows-latest, 3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-python (windows-latest, 3.12)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-python (windows-latest, 3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-python (windows-latest, 3.13)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Notice
The next step is expected to fail.
Test actions / Test setup-python (windows-latest, 3.9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (windows-latest, 3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-python (windows-latest, pypy3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (windows-latest, pypy3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (windows-latest, 3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (windows-latest, 3.9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test analyze-project in root of repo (windows-latest, 3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test analyze-project in root of repo (windows-latest, 3.9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test analyze-project in root of repo (windows-latest, 3.13)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test analyze-project in root of repo (windows-latest, pypy3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test analyze-project in root of repo (windows-latest, pypy3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test analyze-project in root of repo (windows-latest, 3.12)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (windows-latest, 3.13)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test analyze-project in root of repo (windows-latest, 3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-python (windows-latest, pypy3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (windows-latest, 3.12)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-python (windows-latest, 3.13t)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test analyze-project (windows-latest, 3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test analyze-project (windows-latest, 3.13)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test analyze-project (windows-latest, 3.12)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (windows-latest, pypy3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test analyze-project (windows-latest, 3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (cache hit) (windows-latest, 3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (cache hit) (windows-latest, 3.12)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test analyze-project (windows-latest, pypy3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (no cache) (windows-latest, 3.9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (no cache) (windows-latest, 3.12)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (cache hit) (windows-latest, 3.13)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (no cache) (windows-latest, 3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (cache hit) (windows-latest, pypy3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (no cache) (windows-latest, 3.13)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (cache hit) (windows-latest, pypy3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (no cache) (windows-latest, pypy3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test analyze-project (windows-latest, 3.9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (no cache) (windows-latest, 3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (cache hit) (windows-latest, 3.9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (no cache) (windows-latest, pypy3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test analyze-project (windows-latest, pypy3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test actions / Test setup-poetry (cache hit) (windows-latest, 3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677