[releng release-5.13] gromit: sync templates

[probelabs]

Auto-generated from gromit templates by policy sync.

[sentinelone-cnapp-eu1]

SentinelOne CNS Hardcoded Secret Detector
✅ Congratulations, your code is safe

SentinelOne CNS is a cloud-agnostic, agentless CSPM & CWPP solution that continuously detects and prevents vulnerabilities that have the highest probability of being exploited in Azure, AWS, Google Cloud, and Kubernetes.

[probelabs]

This PR updates the Go module cache key within the .github/workflows/release.yml workflow. The change is an automated template synchronization to prevent CI/CD cache collisions.

Files Changed Analysis

• .github/workflows/release.yml: Modified to use a more specific cache key for Go modules. The key was changed from ${{ runner.os }}-go- to ${{ runner.os }}-go-tyk-goreleaser-. This prevents the workflow from incorrectly using caches from other jobs, such as dashboard or pump builds, which could lead to build inconsistencies.

Architecture & Impact Assessment

• What this PR accomplishes: It resolves a potential bug in the CI/CD pipeline where different Go-based builds could inadvertently share the same dependency cache, leading to unpredictable build behavior. By making the cache key more specific, it ensures the release workflow is isolated and uses the correct dependencies.
• Key technical changes: The key and restore-keys for the actions/cache step in the release workflow have been updated to be more specific.
• Affected system components: This change affects the Continuous Integration (CI) pipeline, specifically the release workflow. The impact is improved build reliability and correctness.

Scope Discovery & Context Expansion

• The change is confined to the release.yml workflow. However, the comments added in the diff imply that other workflows might suffer from the same issue of overly broad cache keys (e.g., -go-dashboard-, -go-tyk-pump-).
• To expand the context, a search across all files in .github/workflows/ for the pattern actions/cache with a key like ${{ runner.os }}-go- would be prudent to identify and fix other potential cache collision issues across the repository's CI jobs.

Metadata

• Review Effort: 1 / 5
• Primary Label: chore

---

Powered by Visor from Probelabs

Last updated: 2026-09-11T06:12:56.471Z | Triggered by: pr_opened | Commit: a4ea306

💡 TIP: You can chat with Visor using /visor ask <your question>

[github-actions]

🚨 Jira Linter Failed

Commit: a4ea306
Failed at: 2026-09-11 06:12:42 UTC

The Jira linter failed to validate your PR. Please check the error details below:

🔍 Click to view error details

failed to get Jira issue: Jira issue RELEASE-5 not found (HTTP 404). The issue may exist but the API token may lack permission to access it. Verify that the token owner has access to the project and that JL_JIRA_BASEURL (https://api.atlassian.com/ex/jira/c25a3295-62f6-4d5a-8ddd-58122b144a37) is correct

Next Steps

• Ensure your branch name contains a valid Jira ticket ID (e.g., ABC-123)
• Verify your PR title matches the branch's Jira ticket ID
• Check that the Jira ticket exists and is accessible

---

This comment will be automatically deleted once the linter passes.

[probelabs]

✅ Security Check Passed

No security issues found – changes LGTM.

✅ Architecture Check Passed

No architecture issues found – changes LGTM.

✅ Performance Check Passed

No performance issues found – changes LGTM.

---

Powered by Visor from Probelabs

Last updated: 2026-09-11T06:12:54.192Z | Triggered by: pr_opened | Commit: a4ea306

💡 TIP: You can chat with Visor using /visor ask <your question>

[github-actions]

zizmor findings

Severity	Count
High	27
Medium	68
Low	8
Info	24

Full details are in the workflow run.

[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