Skip to content

feat: bump go to 1.24.0#6932

Merged
kruskall merged 8 commits intoelastic:mainfrom
kruskall:feat/bump-go-1.24
Mar 6, 2025
Merged

feat: bump go to 1.24.0#6932
kruskall merged 8 commits intoelastic:mainfrom
kruskall:feat/bump-go-1.24

Conversation

@kruskall
Copy link
Copy Markdown
Member

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?
  • ...

@kruskall kruskall added the enhancement New feature or request label Feb 19, 2025
@kruskall kruskall requested a review from a team as a code owner February 19, 2025 19:50
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Feb 19, 2025

This pull request does not have a backport label. Could you fix it @kruskall? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-./d./d is the label that automatically backports to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

@kruskall kruskall requested a review from a team as a code owner February 19, 2025 20:18
@cmacknz cmacknz added the backport-8.x Automated backport to the 8.x branch with mergify label Feb 19, 2025
cmacknz
cmacknz previously approved these changes Feb 19, 2025
Copy link
Copy Markdown
Member

@cmacknz cmacknz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Set the backport 8.x label so that 9.1.0 and 8.19 will both release with Go 1.24.

Copy link
Copy Markdown
Contributor

@pkoutsovasilis pkoutsovasilis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would like first the PR that adds the container packaging step in the CI and then merge this PR if our CI is green. Sorry for the delay

cc @dliappis

@dliappis
Copy link
Copy Markdown
Contributor

I would like first the PR that adds the container packaging step in the CI and then merge this PR if our CI is green. Sorry for the delay

cc @dliappis

Agreed. I'd like to tread carefully here, and I don't see a pressing need to go to 1.24.0 right now since 1.23 is still supported.

@kruskall
Copy link
Copy Markdown
Member Author

Agreed. I'd like to tread carefully here, and I don't see a pressing need to go to 1.24.0 right now since 1.23 is still supported.

This is true but 1.24 makes it a lot easier to test/prepare for fips compliance 🙂

I'd prefer not to delay this too much, (I'm also happy to tackle any required issue).

@jlind23
Copy link
Copy Markdown
Contributor

jlind23 commented Feb 24, 2025

@dliappis @kruskall anything else than the eng prod review missing here? I can see that Craig approved and CI is green.

@dliappis
Copy link
Copy Markdown
Contributor

@dliappis @kruskall anything else than the eng prod review missing here? I can see that Craig approved and CI is green.

Quality is paramount and don't want to land in a situation like #6948 where PR passed, but subsequent packaging jobs failed.

I'd prefer not merging until we are sure that CI has the additional coverage mentioned in the linked issue above.

@simitt
Copy link
Copy Markdown
Contributor

simitt commented Feb 24, 2025

We are really eager to get the update to go-1.24 in for easier handling with the FIPS work. But I agree we should have a high confidence level. @dliappis, are you referring to https://github.com/elastic/ingest-dev/issues/5115? Anything that we can help drive forward so that this PR can be driven forward?

I would like first the PR that adds the container packaging step in the CI and then merge this PR if our CI is green.

@pkoutsovasilis which PR or issue are you referring to?

@pkoutsovasilis
Copy link
Copy Markdown
Contributor

I would like first the PR that adds the container packaging step in the CI and then merge this PR if our CI is green.

@pkoutsovasilis which PR or issue are you referring to?

@simitt I can assure you that everybody wants to see this PR merged ASAP and everyone understands the critically of go 1.24 for FIPS. That said, this PR is currently missing but it is being worked on, so we can introduce go 1.24 with confidence that we won't run into any similar issue as we did for go 1.23 (#6948) 🙂

@simitt
Copy link
Copy Markdown
Contributor

simitt commented Feb 24, 2025

@pkoutsovasilis thanks for linking the PR! My comment was not to create more pressure, I was simply not sure which PR is considered a precondition. The go.1.24 update will make certain things easier, but it is not currently blocking us, so I fully agree with stabilizing things first and having a good confidence level.

@swiatekm
Copy link
Copy Markdown
Member

swiatekm commented Mar 3, 2025

Packaging tests are failing because we're using the 1.23 crossbuild image to build the fips docker image. I'm guessing we missed a Go version update somewhere?

@kruskall kruskall added the backport-9.0 Automated backport to the 9.0 branch label Mar 4, 2025
@simitt
Copy link
Copy Markdown
Contributor

simitt commented Mar 5, 2025

#6972 has been merged, @kruskall can you update this branch and then re-request a review? (might update to go-1.24.1 already though, see elastic/golang-crossbuild#529 -> let's stick with 1.24.0 for now as 1.24.1 PR is failing and don't want to be blocked until a new image can be released)

@kruskall
Copy link
Copy Markdown
Member Author

kruskall commented Mar 5, 2025

@elastic/ingest-eng-prod friendly ping for review 🙂

@simitt
Copy link
Copy Markdown
Contributor

simitt commented Mar 6, 2025

buildkite test this

@elastic-sonarqube
Copy link
Copy Markdown

@elasticmachine
Copy link
Copy Markdown
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

History

cc @kruskall

@kruskall kruskall merged commit 79c9886 into elastic:main Mar 6, 2025
14 checks passed
@kruskall kruskall deleted the feat/bump-go-1.24 branch March 6, 2025 14:40
mergify bot pushed a commit that referenced this pull request Mar 6, 2025
* 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)
mergify bot pushed a commit that referenced this pull request Mar 6, 2025
* 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
@kruskall kruskall added the backport-8.18 Automated backport to the 8.18 branch label Mar 6, 2025
@kruskall
Copy link
Copy Markdown
Member Author

kruskall commented Mar 6, 2025

@Mergifyio backport 8.18

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Mar 6, 2025

backport 8.18

✅ Backports have been created

Details

mergify bot pushed a commit that referenced this pull request Mar 6, 2025
* 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
kruskall added a commit that referenced this pull request Mar 6, 2025
* feat: bump go to 1.24.0 (#6932)

* 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

* Update golangci-lint.yml

* Update .golangci.yml

---------

Co-authored-by: kruskall <99559985+kruskall@users.noreply.github.com>
v1v added a commit to pkoutsovasilis/elastic-agent that referenced this pull request Mar 6, 2025
* upstream/main:
  feat: bump go to 1.24.0 (elastic#6932)
  [CI] Fix Core DRA crossbuild (elastic#7203)
  fix(ci): Use correct `READ_ONLY` access value instead of `READ` (elastic#7239)
  ci(buildkite): add initial elastic-agent-helm-charts pipeline (elastic#7176)
  chore: update elastic-agent-libs to v0.18.8 (elastic#6938)
  [flakiness] Correct group for TestEndpointAgentServiceMonitoring (elastic#7165)
kruskall added a commit that referenced this pull request Mar 6, 2025
* feat: bump go to 1.24.0 (#6932)

* 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

* Update golangci-lint.yml

* Update .golangci.yml

---------

Co-authored-by: kruskall <99559985+kruskall@users.noreply.github.com>
simitt pushed a commit that referenced this pull request Mar 10, 2025
* 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)

Co-authored-by: kruskall <99559985+kruskall@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-8.x Automated backport to the 8.x branch with mergify backport-8.18 Automated backport to the 8.18 branch backport-9.0 Automated backport to the 9.0 branch enhancement New feature or request Team:Ingest-EngProd

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants