Skip to content

Fix Content-Type header in S3 proxy #1646

Fix Content-Type header in S3 proxy

Fix Content-Type header in S3 proxy #1646

Triggered via push August 22, 2024 16:46
Status Success
Total duration 3m 16s
Artifacts

ecr_api.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, aws-actions/configure-aws-credentials@v1. 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 use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, aws-actions/configure-aws-credentials@v1, aws-actions/amazon-ecr-login@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build
Your docker password is not masked. See https://github.com/aws-actions/amazon-ecr-login#docker-credentials for more information.