Skip to content

Changed expired nodes to latest ones #130

Changed expired nodes to latest ones

Changed expired nodes to latest ones #130

Triggered via pull request September 25, 2024 08:08
Status Failure
Total duration 10s
Artifacts

conventional-prs.yaml

on: pull_request_target
title-format
2s
title-format
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
title-format
No release type found in pull request title "Changed expired nodes to latest ones". Add a prefix to indicate what kind of release this pull request corresponds to (see https://www.conventionalcommits.org/). 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
title-format
The following actions uses node12 which is deprecated and will be forced to run on node16: amannn/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
title-format
The following actions use a deprecated Node.js version and will be forced to run on node20: amannn/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/