Skip to content

Implement RFC 7523 JWT flows #2409

Implement RFC 7523 JWT flows

Implement RFC 7523 JWT flows #2409

Triggered via pull request August 7, 2025 21:44
Status Success
Total duration 3m 4s
Artifacts

pull-request-checks.yml

on: pull_request
checks  /  pre-commit
27s
checks / pre-commit
checks  /  readme-snippets
12s
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>0gx6VaAAAAAADWN/lUA3xSK9KE4Ln/p56QkwyQUEyMDMwMTA2MDAzAEVkZ2U=
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>0hR6VaAAAAADXb9bfR2cGRbPXzvFAzTZaUEFPRURHRTA2MDkARWRnZQ==
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>0iB6VaAAAAADKAu1AfIw6T5EG217jANitUEhYMzFFREdFMDIxMgBFZGdl
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>0hx6VaAAAAAB7O/H3BIEXT5eM8zhacaXnUEFPRURHRTA2MjEARWRnZQ==
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>0yh6VaAAAAAC5PPSK5SIaSqwWKXu/MdfKQ0gxRURHRTIxMTYARWRnZQ==
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>0yh6VaAAAAABtPc32sj4LT7+aBvaNfpCoQ0gxRURHRTE0MTYARWRnZQ==
checks / test (3.11, 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>0zh6VaAAAAABe/ZZxyrU/TLC19gOEi4UCQ0hJMzBFREdFMDMxNABFZGdl
checks / test (3.13, 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>0+h6VaAAAAAC7Ybga642ZSqVONOIifHoAQkwyQUEyMDMwMTA1MDAzAEVkZ2U=
checks / test (3.12, 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.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
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