v3 Provider appears to randomly remove helm_release resources from TF state - Hard to reproduce #2355
Triggered via issue
March 12, 2026 21:06
Status
Success
Total duration
10s
Artifacts
–
issue-comment-created.yml
on: issue_comment
issue_comment_triage
4s
Annotations
1 error and 3 warnings
|
issue_comment_triage
Error: failed to remove labels: stale,waiting-response
|
|
issue_comment_triage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-ecosystem/action-remove-labels@2ce5d41b4b6aa8503e285553f75ed56e0a40bae0. 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/
|
|
issue_comment_triage
failed to remove label: waiting-response: HttpError: Label does not exist
|
|
issue_comment_triage
failed to remove label: stale: HttpError: Label does not exist
|