Skip to content

Potential fix for code scanning alert no. 4: Workflow does not contain permissions #1

Potential fix for code scanning alert no. 4: Workflow does not contain permissions

Potential fix for code scanning alert no. 4: Workflow does not contain permissions #1

Re-run triggered August 6, 2025 04:39
Status Failure
Total duration 2m 33s
Artifacts

pull-request-checks.yml

on: pull_request
checks  /  pre-commit
25s
checks / pre-commit
checks  /  readme-snippets
13s
checks / readme-snippets
Matrix: checks / test
Fit to window
Zoom out
Zoom in

Annotations

1 error, 16 warnings, and 4 notices
checks / pre-commit
Process completed with exit code 1.
checks / test (3.11, ubuntu-latest)
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>0ptySaAAAAAC+5qM0yngyT7Hkgiztjh61QkwyQUEyMDMwMTA3MDI3AEVkZ2U=
checks / test (3.11, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.13, ubuntu-latest)
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>0qNySaAAAAAAdaP3iYFD7S7VfkNJd7jmpQ0hJMzBFREdFMDIxNQBFZGdl
checks / test (3.13, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.12, ubuntu-latest)
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>0qNySaAAAAADV6V205SaCQpfAeQYVK0PHRE0yRURHRTEwMTYARWRnZQ==
checks / test (3.12, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, ubuntu-latest)
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>0qNySaAAAAAD1XUZ80NJTTZXo56bpmoGLQ0gxRURHRTEyMTEARWRnZQ==
checks / test (3.10, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, windows-latest)
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>07dySaAAAAACoUVdqiRGDRq3UZzMbD8fUQ0gxRURHRTA4MTMARWRnZQ==
checks / test (3.10, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.11, windows-latest)
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>079ySaAAAAACMdk9ruypwSqYRjJw2K2USQkwyQUEyMDMwMTA5MDA1AEVkZ2U=
checks / test (3.11, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.12, windows-latest)
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>08tySaAAAAAAiacDUq/LKRY1HK7C5SDWFQkwyQUEyMDMwMTA3MDM3AEVkZ2U=
checks / test (3.12, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.13, windows-latest)
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>0/dySaAAAAADRE1cBWCahQZFm4enrKXFKQ0hHRURHRTE3MTIARWRnZQ==
checks / test (3.13, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, windows-latest)
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
checks / test (3.11, windows-latest)
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
checks / test (3.12, windows-latest)
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
checks / test (3.13, windows-latest)
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