Implement RFC 7523 JWT flows #2513
pull-request-checks.yml
on: pull_request
checks
/
pre-commit
16s
checks
/
readme-snippets
9s
Matrix: checks / test
Annotations
3 errors, 30 warnings, and 8 notices
|
checks / pre-commit
Process completed with exit code 1.
|
|
checks / test (3.10, highest, windows-latest)
Process completed with exit code 1.
|
|
checks / test (3.10, lowest-direct, windows-latest)
Process completed with exit code 1.
|
|
checks / test (3.10, highest, 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>0amqnaAAAAAC6W9TcEv2IQImfAk/0pD1BQkwyQUEyMDMwMTA1MDMxAEVkZ2U=
|
|
checks / test (3.10, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.12, highest, 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>0a2qnaAAAAADiU9mxG367RI0y4sZFMwexUEhYMzFFREdFMDYxNgBFZGdl
|
|
checks / test (3.12, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.12, lowest-direct, 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>0a2qnaAAAAAAOYeBvAJyMRoWs1i6fxw9mUEFPRURHRTA1MjAARWRnZQ==
|
|
checks / test (3.12, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.13, highest, 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>0a2qnaAAAAAD/zf1A0VvzTbDhdPRq94HGQlkzRURHRTA1MTYARWRnZQ==
|
|
checks / test (3.13, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.11, highest, 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>0cGqnaAAAAAAOIqY/KrG4SLAymiJ+rHMdQkwyQUEyMDMwMTA5MDUxAEVkZ2U=
|
|
checks / test (3.11, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.13, lowest-direct, 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>0cWqnaAAAAACxjnvjbcGfRLu5kDb2kidYQkwyQUEyMDMwMTA2MDM3AEVkZ2U=
|
|
checks / test (3.13, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.11, lowest-direct, 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>0cGqnaAAAAABXi4nQoqTGT45aymm4MsaLQlkzRURHRTA0MTAARWRnZQ==
|
|
checks / test (3.11, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.10, lowest-direct, 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>0c2qnaAAAAAAWNnt1j2RiSYHjASp1RWGLQkwyQUEyMDMwMTA3MDAzAEVkZ2U=
|
|
checks / test (3.10, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.10, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.11, highest, 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>0kGqnaAAAAACQsSxNrjMdR5FYRL8zk2loQkwyQUEyMDMwMTA1MDQ1AEVkZ2U=
|
|
checks / test (3.11, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.13, highest, 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>0lGqnaAAAAABGppv1ptCpSKPkyNqSQwohQkwyQUEyMDMwMTA3MDI3AEVkZ2U=
|
|
checks / test (3.13, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.12, lowest-direct, 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>0k2qnaAAAAAAOImuOUb7sQJgGPqc+wKlFUEhYMzFFREdFMDIwOABFZGdl
|
|
checks / test (3.12, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.11, lowest-direct, 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>0k2qnaAAAAACCILlWuZRATaHKKviesdBuUEhYMzFFREdFMDIxMABFZGdl
|
|
checks / test (3.11, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.13, lowest-direct, 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>0lmqnaAAAAACzSxUefKcbTb3tUuJrBdN0UEhYMzFFREdFMDIxOQBFZGdl
|
|
checks / test (3.13, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.12, highest, 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>0mmqnaAAAAAAdbSD/JX/KRqMUJuaS65WlQkwyQUEyMDMwMTA3MDQ1AEVkZ2U=
|
|
checks / test (3.12, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.10, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.10, highest, 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, highest, 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, highest, 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, lowest-direct, 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, lowest-direct, 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, lowest-direct, 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, highest, 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.10, lowest-direct, 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
|