Skip to content

[cisco-sg] add poe support #415

[cisco-sg] add poe support

[cisco-sg] add poe support #415

Triggered via push June 24, 2026 10:24
Status Failure
Total duration 1m 17s
Artifacts
Slack start message
6s
Slack start message
codespell
10s
codespell
Slack final status
7s
Slack final status
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 4 warnings
codespell: docs/Gemfile.lock#L223
rouge ==> rogue
codespell: docs/Gemfile.lock#L109
rouge ==> rogue
codespell: docs/Gemfile.lock#L72
rouge ==> rogue
storybook
Process completed with exit code 1.
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/