Skip to content
Rebase onto upstream

Rebase onto upstream #2715

Sign in to view logs

Rebase onto upstream

Rebase onto upstream #2715

Triggered via schedule November 12, 2024 00:22
@zxaoszxaos
⁠ 6036c4a
readme-and-settings
Status Success
Total duration 36s
Artifacts –

rebase-upstream.yml

on: schedule
Matrix: update branches from upstream
Fit to window
Zoom out
Zoom in

Annotations

12 warnings
update branches from upstream (master-netlify, master)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, zxaos/patchup@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
update branches from upstream (master-netlify, master)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, zxaos/patchup@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
update branches from upstream (master, master)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, zxaos/patchup@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
update branches from upstream (master, master)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, zxaos/patchup@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
update branches from upstream (9.1.x, 9.1.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, zxaos/patchup@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
update branches from upstream (9.1.x-netlify, 9.1.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, zxaos/patchup@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
update branches from upstream (9.1.x, 9.1.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, zxaos/patchup@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
update branches from upstream (9.1.x-netlify, 9.1.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, zxaos/patchup@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
update branches from upstream (9.2.x, 9.2.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, zxaos/patchup@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
update branches from upstream (9.2.x, 9.2.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, zxaos/patchup@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
update branches from upstream (9.2.x-netlify, 9.2.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, zxaos/patchup@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
update branches from upstream (9.2.x-netlify, 9.2.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, zxaos/patchup@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/