[9.0](backport #4543) Update to go v1.24.0 #4553
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
Update to go v1.24.0, change golang.org/x/crypto/pbkdf2 to crypto/pbkdf2 (cherry picked from commit c2b8d66)
github-actions
bot
added
enhancement
|
buildkite test this |
1 similar comment
|
buildkite test this |
michel-laterman
approved these changes
Mar 6, 2025
|
Looks like E2E tests time out on creating the Elastic Cloud deployment. That doesn't appear to be related to any changes in this PR. |
|
This pull request has not been merged yet. Could you please review and merge it @michel-laterman? 🙏 |
|
buildkite test this |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the problem this PR solves?
Update to go v1.24.0, change golang.org/x/crypto/pbkdf2 to crypto/pbkdf2
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 areasI have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature works./changelog/fragmentsusing the changelog toolThis is an automatic backport of pull request Update to go v1.24.0 #4543 done by Mergify.