feat(medium): Fix: Spotify 'Connect' button persists after successful connection #8227
ariicomment-ops.yml
on: issue_comment
🔍 Route Comment
4s
init-status
3s
execute-help
0s
execute-triage
/
disabled-guidance
execute-triage
/
maintenance
execute-triage
/
triage
execute-enrich
/
Enrich PR Title and Description
execute-coder
/
ai-developer
execute-coder
/
disabled-guidance
execute-create-review-issues
/
Create Issues from Gemini Review
execute-create-review-issues
/
disabled-guidance
execute-squash
/
check-for-changes-after-squash
7s
execute-squash
/
trigger-ci-workflow
4s
finalize-status
3s
🚀 Create Review Issues
/
Create Issues from Gemini Review
🚀 Create Review Issues
/
disabled-guidance
Annotations
1 error and 4 warnings
|
execute-squash / trigger-ci-workflow
Process completed with exit code 1.
|
|
init-status
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: peter-evans/create-or-update-comment@v4. 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/
|
|
execute-squash / squash-and-rebase
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/github-script@v6. 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/
|
|
execute-squash / check-for-changes-after-squash
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|
|
finalize-status
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: peter-evans/create-or-update-comment@v4. 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/
|