Skip to content

fix: usage of potentially wrong melos version during script execution #1520

fix: usage of potentially wrong melos version during script execution

fix: usage of potentially wrong melos version during script execution #1520

Triggered via pull request October 29, 2024 13:11
@bspinnerbspinner
edited #783
Status Failure
Total duration 17s
Artifacts

pr_title.yaml

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

Annotations

1 error and 2 warnings
Validate PR title
Unknown release type "Fix" found in pull request title "Fix: usage of potentially wrong melos version during script execution". 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/[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/
Validate PR title
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/