Skip to content

Implement RFC 7523 JWT flows #2410

Implement RFC 7523 JWT flows

Implement RFC 7523 JWT flows #2410

Triggered via pull request August 7, 2025 21:48
Status Success
Total duration 2m 27s
Artifacts

pull-request-checks.yml

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

Annotations

16 warnings and 4 notices
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>0WB+VaAAAAABac6tWIcAKSaTAT9Pm/JnAQkwyQUEyMDMwMTA4MDM5AEVkZ2U=
checks / test (3.11, 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>0Wh+VaAAAAAD1rj0hz0tNQYwnUrpEGwcTRE0yRURHRTA5MTkARWRnZQ==
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>0XB+VaAAAAADcprUWY0qlS4jSdAQ543sDUEhYMzFFREdFMDIwNwBFZGdl
checks / test (3.10, 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>0YR+VaAAAAACLOTveBKbNRIyUYNG/MeScQkwyQUEyMDMwMTA1MDE5AEVkZ2U=
checks / test (3.13, 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>0mB+VaAAAAADCSFFXxNYvTbErEkFd1ux0QkwyQUEyMDMwMTA3MDE3AEVkZ2U=
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>0oB+VaAAAAAD8Z9eW8y51RrRS0/hT0ZcyQkwyQUEyMDMwMTA1MDMxAEVkZ2U=
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>0oh+VaAAAAAA6rBpRtt2pQrTCepnoHBesQkwyQUEyMDMwMTA5MDA3AEVkZ2U=
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>0rB+VaAAAAAAemkVMzTtBR4KPP9hHRa0LQkwyQUEyMDMwMTA1MDI3AEVkZ2U=
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