Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.16](backport #4555) Update pipeline.package.mbp.yml #4559

Merged
merged 2 commits into from
Mar 6, 2025

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Mar 6, 2025

GVM is unable to install Go 1.24.0 on main due to a missing fix that landed in 0.5.1

What is the problem this PR solves?

// Please do not just reference an issue. Explain WHAT the problem this PR solves here.

How does this PR solve the problem?

// Explain HOW you solved the problem in your code. It is possible that during PR reviews this changes and then this section should be updated.

How to test this PR locally

Design Checklist

  • I have ensured my design is stateless and will work when multiple fleet-server instances are behind a load balancer.
  • I have or intend to scale test my changes, ensuring it will work reliably with 100K+ agents connected.
  • I have included fail safe mechanisms to limit the load on fleet-server: rate limiting, circuit breakers, caching, load shedding, etc.

Checklist

  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in ./changelog/fragments using the changelog tool

Related issues


This is an automatic backport of pull request #4555 done by [Mergify](https://mergify.com).

GVM is unable to install Go 1.24.0 on main due to a missing fix that landed in 0.5.1

(cherry picked from commit 20c2254)

# Conflicts:
#	.buildkite/pipeline.yml
@mergify mergify bot requested a review from a team as a code owner March 6, 2025 11:33
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Mar 6, 2025
@mergify mergify bot assigned jlind23 Mar 6, 2025
Copy link
Contributor Author

mergify bot commented Mar 6, 2025

Cherry-pick of 20c2254 has failed:

On branch mergify/bp/8.16/pr-4555
Your branch is up to date with 'origin/8.16'.

You are currently cherry-picking commit 20c2254.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   .buildkite/pipeline.package.mbp.yml
	modified:   .buildkite/scripts/common.sh

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .buildkite/pipeline.yml

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@jlind23
Copy link
Contributor

jlind23 commented Mar 6, 2025

buildkite test it

@jlind23 jlind23 enabled auto-merge (squash) March 6, 2025 11:50
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@jlind23 jlind23 merged commit a79f5de into 8.16 Mar 6, 2025
8 checks passed
@jlind23 jlind23 deleted the mergify/bp/8.16/pr-4555 branch March 6, 2025 14:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport conflicts There is a conflict in the backported pull request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant