Skip to content

add S3 compatibility #1

add S3 compatibility

add S3 compatibility #1

Triggered via pull request July 25, 2024 09:46
Status Failure
Total duration 24s
Artifacts

validate-pr-title.yml

on: pull_request
Validate PR title against conventional commit
4s
Validate PR title against conventional commit
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
Validate PR title against conventional commit
No release type found in pull request title "add S3 compatibility". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/ Available types: - feat - feature - fix - bugfix - improvements - enhancement - perf - build - ci - refactor - doc - docs - test - tests - style - chore - other
Validate PR title against conventional commit
The following actions uses node12 which is deprecated and will be forced to run on node16: amannn/action-semantic-pull-request@v4. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Validate PR title against conventional commit
The following actions uses Node.js version which is deprecated and will be forced to run on node20: amannn/action-semantic-pull-request@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Validate PR title against conventional commit
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/