[releng release-5.15] 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 GitHub Actions release workflow to prevent a potential cache collision issue. The Go module cache key has been made more specific to ensure it doesn't conflict with caches from other related projects.

Files Changed Analysis

• .github/workflows/release.yml: Modified (+6, -3)

The change is confined to the release workflow configuration, specifically targeting the caching mechanism for Go modules.

Architecture & Impact Assessment

• What this PR accomplishes: It resolves a potential bug in the CI/CD pipeline where an overly broad cache key (${{ runner.os }}-go-) could cause incorrect cache hits between different jobs or repositories (e.g., tyk-pump, tyk-dashboard).
• Key technical changes introduced: The cache key in the release.yml workflow has been changed from ${{ runner.os }}-go- to the more specific ${{ runner.os }}-go-tyk-goreleaser-. This ensures that the cache is unique to this specific workflow and repository.
• Affected system components: The change affects only the CI/CD release process. There is no impact on the runtime behavior or architecture of the Tyk gateway itself. The primary benefit is improved build reliability and correctness.

Scope Discovery & Context Expansion

• The PR title and description ("gromit: sync templates", "Auto-generated from gromit templates") indicate this change was applied automatically by a policy synchronization tool named "gromit". This suggests the fix is likely being applied across multiple repositories in the Tyk ecosystem to enforce consistent and correct CI/CD practices.
• The code comment explicitly mentions other components (tyk-dashboard, tyk-pump), confirming the cross-repository nature of the cache collision problem this PR solves for the main tyk repository.

Metadata

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

---

Powered by Visor from Probelabs

Last updated: 2026-09-11T06:14:08.583Z | Triggered by: pr_opened | Commit: 1f56561

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

[probelabs]

✅ Security Check Passed

No security issues found – changes LGTM.

✅ Architecture Check Passed

No architecture issues found – changes LGTM.

✅ Security Check Passed

No security issues found – changes LGTM.

\n\n

✅ Architecture Check Passed

No architecture issues found – changes LGTM.

\n\n

✅ Performance Check Passed

No performance issues found – changes LGTM.

---

Powered by Visor from Probelabs

Last updated: 2026-09-11T06:14:05.365Z | Triggered by: pr_opened | Commit: 1f56561

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

[github-actions]

🚨 Jira Linter Failed

Commit: 1f56561
Failed at: 2026-09-11 06:15:02 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.

[github-actions]

zizmor findings

Severity	Count
High	27
Medium	68
Low	8
Info	24

Full details are in the workflow run.