fix(security): remediate CVE vulnerabilities #251
ulucinarci.yml
on: pull_request
detect-noop
7s
report-breaking-changes
8s
lint
4m 21s
check-diff
1m 4s
unit-tests
3m 8s
local-deploy
3m 39s
check-examples
4s
Annotations
10 errors and 7 warnings
|
lint:
internal/opentofu/opentofu.go#L548
os/exec.Command must not be called. use os/exec.CommandContext (noctx)
|
|
lint:
internal/opentofu/opentofu.go#L462
os/exec.Command must not be called. use os/exec.CommandContext (noctx)
|
|
lint:
internal/opentofu/opentofu.go#L402
os/exec.Command must not be called. use os/exec.CommandContext (noctx)
|
|
lint:
internal/opentofu/opentofu.go#L315
os/exec.Command must not be called. use os/exec.CommandContext (noctx)
|
|
lint:
internal/opentofu/opentofu.go#L292
os/exec.Command must not be called. use os/exec.CommandContext (noctx)
|
|
lint:
internal/opentofu/opentofu.go#L272
os/exec.Command must not be called. use os/exec.CommandContext (noctx)
|
|
lint:
internal/opentofu/opentofu.go#L255
os/exec.Command must not be called. use os/exec.CommandContext (noctx)
|
|
lint:
internal/opentofu/opentofu.go#L241
os/exec.Command must not be called. use os/exec.CommandContext (noctx)
|
|
lint:
internal/opentofu/opentofu.go#L206
os/exec.Command must not be called. use os/exec.CommandContext (noctx)
|
|
lint:
internal/opentofu/opentofu.go#L177
os/exec.Command must not be called. use os/exec.CommandContext (noctx)
|
|
detect-noop
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: fkirc/skip-duplicate-actions@f75f66ce1886f00957d99748a42c724f4330bdcf. 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/
|
|
report-breaking-changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: tj-actions/glob@v17.2.5. 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/
|
|
check-diff
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@d35c59abb061a4a6fb18e82ac0862c26744d6ab5, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
check-diff
No files were found with the provided path: _output/skipped_resources.csv. No artifacts will be uploaded.
|
|
unit-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@d35c59abb061a4a6fb18e82ac0862c26744d6ab5. 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/
|
|
local-deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@d35c59abb061a4a6fb18e82ac0862c26744d6ab5. 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/
|
|
lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/setup-go@d35c59abb061a4a6fb18e82ac0862c26744d6ab5. 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/
|