Skip to content

Consistent casing for default headers Accept and Content-Type #2438

Consistent casing for default headers Accept and Content-Type

Consistent casing for default headers Accept and Content-Type #2438

Triggered via pull request August 12, 2025 09:39
Status Success
Total duration 2m 23s
Artifacts

pull-request-checks.yml

on: pull_request
checks  /  pre-commit
24s
checks / pre-commit
checks  /  readme-snippets
11s
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>0+gubaAAAAABlkh/oMo5IQIrxySfiN5rUQkwyQUEyMDMwMTA4MDE3AEVkZ2U=
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>0+wubaAAAAAC4QmgsubI4QbwmgYwnoXSOQkwyQUEyMDMwMTEwMDI3AEVkZ2U=
checks / test (3.12, 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>0/AubaAAAAABD37uo0xvkS4BnXRpdgn9bQkwyQUEyMDMwMTEwMDQ1AEVkZ2U=
checks / test (3.13, 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>0/AubaAAAAABnQOuAVsZkQIRGjzbUPAgyQkwyQUEyMDMwMTA2MDA1AEVkZ2U=
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>0NgybaAAAAAAwoQ5SCQelRqOzlmB9YYBlQkwyQUEyMDMwMTEwMDAzAEVkZ2U=
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>0QQybaAAAAABfBgG3bY0PSqZlicJfqyT8QkwyQUEyMDMwMTA1MDA3AEVkZ2U=
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>0RAybaAAAAADRcmfx8Z6aTZvP5wxsC45TRE0yRURHRTEwMTUARWRnZQ==
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>0RgybaAAAAAB+RaCQtbGwR5R+h8nlBqpgRE0yRURHRTA4MjEARWRnZQ==
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