Skip to content

Fix for s3:CreateBucket not being detected #81 #80

Fix for s3:CreateBucket not being detected #81

Fix for s3:CreateBucket not being detected #81 #80

Triggered via push September 6, 2024 13:33
Status Success
Total duration 4m 20s
Artifacts

release.yaml

on: push
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
goreleaser
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2, apple-actions/import-codesign-certs@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
goreleaser
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-go@v2, apple-actions/import-codesign-certs@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
goreleaser
You are using 'latest' as default version. Will lock to '~> v2'.
goreleaser
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/
goreleaser
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/