Skip to content

feat!: use w3up-client in keyring #151

feat!: use w3up-client in keyring

feat!: use w3up-client in keyring #151

Triggered via pull request November 13, 2023 13:06
@travistravis
opened #581
Status Failure
Total duration 15s
Artifacts

conventional-commits.yml

on: pull_request_target
Validate PR title
5s
Validate PR title
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
Validate PR title
Unknown release type "wip" found in pull request title "wip: use w3up-client in keyring". Available types: - feat: A new feature - fix: A bug fix - docs: Documentation only changes - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) - refactor: A code change that neither fixes a bug nor adds a feature - perf: A code change that improves performance - test: Adding missing tests or correcting existing tests - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm) - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs) - chore: Other changes that don't modify src or test files - revert: Reverts a previous commit
Validate PR title
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
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/