Skip to content

Issue / PR Triage #60476

Issue / PR Triage

Issue / PR Triage #60476

Triggered via schedule September 21, 2024 19:43
Status Success
Total duration 1m 11s
Artifacts

triage.yml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
triage
Label Messager error: request to https://api.github.com/repos/bytecodealliance/wasmtime/issues/7832/comments failed, reason: socket hang up Stack:�HttpError: request to https://api.github.com/repos/bytecodealliance/wasmtime/issues/7832/comments failed, reason: socket hang up at /home/runner/work/_actions/bytecodealliance/label-messager-action/v1/dist/index.js:9690:11 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async triagePullRequests (/home/runner/work/_actions/bytecodealliance/label-messager-action/v1/dist/index.js:1675:24) at async main (/home/runner/work/_actions/bytecodealliance/label-messager-action/v1/dist/index.js:1561:7)
triage
The following actions uses node12 which is deprecated and will be forced to run on node16: bytecodealliance/labeler@schedule-fork, bytecodealliance/subscribe-to-label-action@v1, bytecodealliance/label-messager-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
triage
The following actions use a deprecated Node.js version and will be forced to run on node20: bytecodealliance/labeler@schedule-fork, bytecodealliance/subscribe-to-label-action@v1, bytecodealliance/label-messager-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
triage
performed 30 operations, exiting to avoid rate limit