fix: Addressed architectural review comments (#316) #36
merge-to-next-major.yml
on: push
Perform merge if "next" can merge into "next-major"
5s
Merge failure
0s
Annotations
1 error and 5 warnings
Perform merge if "next" can merge into "next-major"
Process completed with exit code 1.
|
Perform merge if "next" can merge into "next-major"
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Perform merge if "next" can merge into "next-major"
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Perform merge if "next" can merge into "next-major"
Unexpected input(s) 'repo-token', valid inputs are ['repository', 'ref', 'token', 'ssh-key', 'ssh-known-hosts', 'ssh-strict', 'persist-credentials', 'path', 'clean', 'fetch-depth', 'lfs', 'submodules', 'set-safe-directory']
|
Perform merge if "next" can merge into "next-major"
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/
|
Perform merge if "next" can merge into "next-major"
Unexpected input(s) 'repo-token', valid inputs are ['repository', 'ref', 'token', 'ssh-key', 'ssh-known-hosts', 'ssh-strict', 'persist-credentials', 'path', 'clean', 'fetch-depth', 'lfs', 'submodules', 'set-safe-directory']
|