Skip to content

Remind user that cre_settings changes might involve re-proposing job-specs #1

Remind user that cre_settings changes might involve re-proposing job-specs

Remind user that cre_settings changes might involve re-proposing job-specs #1

Triggered via pull request June 5, 2026 11:36
Status Success
Total duration 19s
Artifacts
reminder
8s
reminder
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
reminder
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36, peter-evans/create-or-update-comment@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
reminder
Unexpected input(s) 'body-includes', valid inputs are ['token', 'repository', 'issue-number', 'comment-id', 'body', 'body-path', 'body-file', 'edit-mode', 'append-separator', 'reactions', 'reactions-edit-mode']