chore(deps): update helm/kind-action action to v1.13.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
helm/kind-action	action	minor	v1.12.0 -> v1.13.0

---

Release Notes

helm/kind-action (helm/kind-action)

v1.13.0

Compare Source

What's Changed

• chore: verify sha256sum of kubectl by @​felix-kaestner in #​134
• Load GITHUB_PATH in PATH to use correct binaries when creating registry by @​gotha in #​133
• feat: Add cloud provider by @​waltermity in #​135
• chore: bump kind to v0.29.0 by @​pmalek in #​144
• Bump actions/checkout from 4.2.2 to 5.0.0 by @​dependabot[bot] in #​145
• bug: respect 'install_only' action input value by @​mszostok in #​147
• bump kind and kubectl and also nodejs by @​cpanato in #​150

New Contributors

• @​felix-kaestner made their first contribution in #​134
• @​gotha made their first contribution in #​133
• @​waltermity made their first contribution in #​135
• @​pmalek made their first contribution in #​144
• @​mszostok made their first contribution in #​147

Full Changelog: helm/kind-action@v1...v1.13.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rm3l]

/lgtm

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
🟢	No codebase code duplication found No new components were introduced in the PR code
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[rhdh-qodo-merge]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
🟢	No codebase code duplication found No new components were introduced in the PR code
Custom Compliance
🟢	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: No auditing: The change only updates the action version reference and does not add or modify any audit logging for critical actions in the workflow. Referred Code uses: helm/kind-action@92086f6be054225fa813e0a4b13787fc9088faab # v1.13.0 with: config: /tmp/kind-config.yaml
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: No error handling: The update to the action version does not include any added failure handling, retry logic, or contextual error messaging for the Create KIND Cluster step. Referred Code if: steps.list-changed.outputs.changed == 'true' uses: helm/kind-action@92086f6be054225fa813e0a4b13787fc9088faab # v1.13.0 with: config: /tmp/kind-config.yaml

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label