Skip to content

OAuth Update: Adding the Client Credentials & Token Exchange Grant Types #2679

OAuth Update: Adding the Client Credentials & Token Exchange Grant Types

OAuth Update: Adding the Client Credentials & Token Exchange Grant Types #2679

Triggered via pull request September 17, 2025 17:11
Status Success
Total duration 1m 43s
Artifacts

pull-request-checks.yml

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

Annotations

32 warnings and 8 notices
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>01evKaAAAAACpgjJaiSggRb9GmQHypqI3QkwyQUEyMDMwMTA4MDQ5AEVkZ2U=
checks / test (3.11, 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>01uvKaAAAAACC65m0yaTET7PKYzJlEP7gQkwyQUEyMDMwMTA5MDM1AEVkZ2U=
checks / test (3.13, highest, 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>01+vKaAAAAABFF5xyM+MkQZaS4xg21Iv/QkwyQUEyMDMwMTA4MDI5AEVkZ2U=
checks / test (3.10, lowest-direct, 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>01+vKaAAAAAA6xMlVBm01SIPIuyFkFUUmREVOMzAxMDAwMTA3MDM1AEVkZ2U=
checks / test (3.12, lowest-direct, 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>01uvKaAAAAACVi5+PmAYvTbbR0MkdZB6hQlkzRURHRTAxMTAARWRnZQ==
checks / test (3.12, 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>02evKaAAAAACIaFx19DgSSamjXzsy56skQ0hJMzBFREdFMDQxOABFZGdl
checks / test (3.13, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
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>02OvKaAAAAABQeLaYJkcdQKrIofWc6BG6UEFPRURHRTA1MTkARWRnZQ==
checks / test (3.10, 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>02evKaAAAAAAGTdurULTWRJPli4l/uJ+sQlkzRURHRTA0MjAARWRnZQ==
checks / test (3.11, highest, ubuntu-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>0/+vKaAAAAABxXzMuk4sLQpMrM4Se/RrhQkwyQUEyMDMwMTA4MDQ1AEVkZ2U=
checks / test (3.13, lowest-direct, 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>0AOzKaAAAAAAxSBVciTAzTJFQ2g2j4wy0QkwyQUEyMDMwMTEwMDA5AEVkZ2U=
checks / test (3.13, highest, 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>0BuzKaAAAAADes4atXydQT4wsxUovLK33QkwyQUEyMDMwMTA5MDMzAEVkZ2U=
checks / test (3.12, highest, 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>0AuzKaAAAAACECdh9eDp5RKdJpnQ9mf3nQkwyQUEyMDMwMTA4MDI3AEVkZ2U=
checks / test (3.11, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, 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>0B+zKaAAAAADeUga3G9kMTbZyGkAaxVGYQkwyQUEyMDMwMTA4MDIzAEVkZ2U=
checks / test (3.10, highest, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, 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>0CuzKaAAAAAB+FVkRLkJGRqKYyKhYj2PxUEFPRURHRTA1MTEARWRnZQ==
checks / test (3.10, lowest-direct, 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>0DezKaAAAAADKntiZwW5xQYDLT34Cs0l9QkwyQUEyMDMwMTA5MDA3AEVkZ2U=
checks / test (3.12, lowest-direct, 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>0FezKaAAAAADKwNVz7+uxSYQrgxHA7teAQkwyQUEyMDMwMTA4MDI3AEVkZ2U=
checks / test (3.11, highest, windows-latest)
Failed to restore: Cache service responded with 400
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.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, 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, 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.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.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
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, 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