Skip to content

[8.18] feat: bump go to 1.24.0 (backport #6932)#7249

Merged
kruskall merged 3 commits into8.18from
mergify/bp/8.18/pr-6932
Mar 6, 2025
Merged

[8.18] feat: bump go to 1.24.0 (backport #6932)#7249
kruskall merged 3 commits into8.18from
mergify/bp/8.18/pr-6932

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Mar 6, 2025

What does this PR do?

bump go to 1.24.0

Why is it important?

should help with fips among other things

Checklist

  • I have read and understood the pull request guidelines of this project.
  • My code follows the style guidelines of this project
  • 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
  • I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

  • How are we going to support this in production?
  • How are we going to measure its adoption?
  • How are we going to debug this?
  • What are the metrics I should take care of?
  • ...

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

* feat: bump go to 1.24.0

* lint: bump golangci-lint

* lint: bump golangci-lint

* Update .golangci.yml

* Update .golangci.yml

* build: bump go to 1.24.0

(cherry picked from commit 79c9886)

# Conflicts:
#	.github/workflows/golangci-lint.yml
#	.golangci.yml
@mergify mergify bot requested review from a team as code owners March 6, 2025 15:41
@mergify mergify bot added the conflicts There is a conflict in the backported pull request label Mar 6, 2025
@mergify
Copy link
Copy Markdown
Contributor Author

mergify bot commented Mar 6, 2025

Cherry-pick of 79c9886 has failed:

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

You are currently cherry-picking commit 79c988688.
  (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.yml
	modified:   .go-version
	modified:   .tool-versions
	modified:   Dockerfile
	modified:   Dockerfile.skaffold
	modified:   Makefile
	modified:   changelog/fragments/1723829102-Upgrade-to-Go-1.23.0.yaml
	modified:   go.mod
	modified:   pkg/testing/runner/runner_test.go
	modified:   version/docs/version.asciidoc

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .github/workflows/golangci-lint.yml
	both modified:   .golangci.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

@mergify mergify bot requested review from blakerouse and michalpristas and removed request for a team March 6, 2025 15:41
@mergify mergify bot mentioned this pull request Mar 6, 2025
8 tasks
@github-actions github-actions bot added enhancement New feature or request Team:Ingest-EngProd labels Mar 6, 2025
@swiatekm swiatekm changed the title feat: bump go to 1.24.0 (backport #6932) [8.18] feat: bump go to 1.24.0 (backport #6932) Mar 6, 2025
@kruskall kruskall removed the conflicts There is a conflict in the backported pull request label Mar 6, 2025
@kruskall kruskall enabled auto-merge (squash) March 6, 2025 18:28
@elastic-sonarqube
Copy link
Copy Markdown

@kruskall kruskall merged commit 2291e9b into 8.18 Mar 6, 2025
14 checks passed
@kruskall kruskall deleted the mergify/bp/8.18/pr-6932 branch March 6, 2025 21:51
@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

History

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants