Skip to content

v1.8.1

v1.8.1 #16

Triggered via release March 14, 2026 01:11
@McTalianMcTalian
published v1.8.1
Status Success
Total duration 46s
Artifacts
package-and-release  /  release
35s
package-and-release / release
package-and-release  /  announce
5s
package-and-release / announce
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
package-and-release / release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache/save@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
package-and-release / announce
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: tsickert/discord-webhook@b217a69502f52803de774ded2b1ab7c282e99645. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/