Version Bump #828
Triggered via workflow run
July 21, 2026 09:38
geoffhouse
completed
e19ba32
Status
Failure
Total duration
19s
Artifacts
–
versioning.yml
on: workflow_run
Verify required tests passed
6s
Slack start message
6s
Slack final status
6s
Annotations
1 error and 5 warnings
|
Verify required tests passed
Process completed with exit code 1.
|
|
Verify required tests passed
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/github-script@v7. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Slack start message
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: slackapi/slack-github-action@v2.1.1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Slack start message
Additionally, the attachment-level `fallback` argument is missing in the request payload for a chat.postMessage call - To avoid this warning, it is recommended to always provide a top-level `text` argument when posting a message. Alternatively, you can provide an attachment-level `fallback` argument, though this is now considered a legacy field (see https://api.slack.com/reference/messaging/attachments#legacy_fields for more details).
|
|
Slack start message
The top-level `text` argument is missing in the request payload for a chat.postMessage call - It's a best practice to always provide a `text` argument when posting a message. The `text` is used in places where the content cannot be rendered such as: system push notifications, assistive technology such as screen readers, etc.
|
|
Slack final status
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: slackapi/slack-github-action@v2.1.1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|