Skip to content

chore(deps): update release-drafter/release-drafter action to v7 #238

chore(deps): update release-drafter/release-drafter action to v7

chore(deps): update release-drafter/release-drafter action to v7 #238

Triggered via pull request March 18, 2026 20:55
Status Success
Total duration 35s
Artifacts

lint.yml

on: pull_request
Matrix: Build
Fit to window
Zoom out
Zoom in

Annotations

9 warnings
Build (1.22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-go@93397bea11091df50f3d7e59dc26a7711a8bcfbe. 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/
Build (1.22)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0YhG7aQAAAAChnRpaFA7wSY6doAlUvD7IUEhMMzBFREdFMDIyMABFZGdl
Build (1.22)
Failed to restore: Cache service responded with 400
Build (1.21)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-go@93397bea11091df50f3d7e59dc26a7711a8bcfbe. 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/
Build (1.21)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0ZxG7aQAAAADigrKHGgWdT76aFiRjhVg5REVOMzAxMDAwMTA2MDA5AEVkZ2U=
Build (1.21)
Failed to restore: Cache service responded with 400
Build (1.20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-go@93397bea11091df50f3d7e59dc26a7711a8bcfbe. 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/
Build (1.20)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0axG7aQAAAACEproPZS2YQL+uNT1ZN6KsUEhMMzBFREdFMDExMgBFZGdl
Build (1.20)
Failed to restore: Cache service responded with 400