Skip to content

Merging to release-5.14.0: TT-17622: cherry-pick goreleaser timeout bump (#8377)#8378

Merged
lghiur merged 1 commit into
release-5.14.0from
merge/release-5.14.0/d945e02c5a7d9cb6724f96d87c95f3cbb720259d/TT-17622
Jun 25, 2026
Merged

Merging to release-5.14.0: TT-17622: cherry-pick goreleaser timeout bump (#8377)#8378
lghiur merged 1 commit into
release-5.14.0from
merge/release-5.14.0/d945e02c5a7d9cb6724f96d87c95f3cbb720259d/TT-17622

Conversation

@probelabs

@probelabs probelabs Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

TT-17622: cherry-pick goreleaser timeout bump (#8377)

Description

change cherry-picks goreleaser timeout bump

Related Issue

https://tyktech.atlassian.net/browse/TT-17622

Motivation and Context

How This Has Been Tested

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing
    functionality to change)
  • Refactoring or add test (improvements in base code or adds test
    coverage to functionality)

Checklist

  • I ensured that the documentation is up to date
  • I explained why this PR updates go.mod in detail with reasoning
    why it's required
  • I would like a code coverage CI quality gate exception and have
    explained why

<!-- Provide a general summary of your changes in the Title above -->

## Description
change cherry-picks  goreleaser timeout bump
<!-- Describe your changes in detail -->

## Related Issue
https://tyktech.atlassian.net/browse/TT-17622
<!-- This project only accepts pull requests related to open issues. -->
<!-- If suggesting a new feature or change, please discuss it in an
issue first. -->
<!-- If fixing a bug, there should be an issue describing it with steps
to reproduce. -->
<!-- OSS: Please link to the issue here. Tyk: please create/link the
JIRA ticket. -->

## Motivation and Context

<!-- Why is this change required? What problem does it solve? -->

## How This Has Been Tested

<!-- Please describe in detail how you tested your changes -->
<!-- Include details of your testing environment, and the tests -->
<!-- you ran to see how your change affects other areas of the code,
etc. -->
<!-- This information is helpful for reviewers and QA. -->

## Screenshots (if appropriate)

## Types of changes

<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Refactoring or add test (improvements in base code or adds test
coverage to functionality)

## Checklist

<!-- Go over all the following points, and put an `x` in all the boxes
that apply -->
<!-- If there are no documentation updates required, mark the item as
checked. -->
<!-- Raise up any additional concerns not covered by the checklist. -->

- [ ] I ensured that the documentation is up to date
- [ ] I explained why this PR updates go.mod in detail with reasoning
why it's required
- [ ] I would like a code coverage CI quality gate exception and have
explained why

(cherry picked from commit d945e02)
@probelabs
probelabs Bot requested a review from a team as a code owner June 25, 2026 12:40
@sentinelone-cnapp-eu1

Copy link
Copy Markdown

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.

@github-actions

Copy link
Copy Markdown
Contributor

🚨 Jira Linter Failed

Commit: 52e1944
Failed at: 2026-06-25 12:41:17 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: failed to fetch Jira issue TT-17622: Issue does not exist or you do not have permission to see it.: request failed. Please analyze the request body for more details. Status code: 404

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

probelabs Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor Author

Powered by Visor from Probelabs

Last updated: 2026-06-25T12:41:18.544Z | Triggered by: pr_opened | Commit: 52e1944

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

@probelabs

probelabs Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor Author
\n\n \n\n \n\n

Powered by Visor from Probelabs

Last updated: 2026-06-25T12:41:19.527Z | Triggered by: pr_opened | Commit: 52e1944

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

@sonarqubecloud

Copy link
Copy Markdown

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

@lghiur
lghiur merged commit 237d450 into release-5.14.0 Jun 25, 2026
24 of 27 checks passed
@lghiur
lghiur deleted the merge/release-5.14.0/d945e02c5a7d9cb6724f96d87c95f3cbb720259d/TT-17622 branch June 25, 2026 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants