Skip to content

Clarify server behavior if content type is not supported #1256

Clarify server behavior if content type is not supported

Clarify server behavior if content type is not supported #1256

Triggered via pull request July 8, 2024 13:48
Status Success
Total duration 33s
Artifacts

main.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/