Conversation
|
This pull request does not have a backport label. Could you fix it @kruskall? 🙏
|
cmacknz
left a comment
There was a problem hiding this comment.
Thanks! Set the backport 8.x label so that 9.1.0 and 8.19 will both release with Go 1.24.
pkoutsovasilis
left a comment
There was a problem hiding this comment.
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. |
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). |
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. |
|
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?
@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) 🙂 |
|
@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. |
|
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? |
|
#6972 has been merged, @kruskall can you update this branch and then re-request a review? ( |
|
@elastic/ingest-eng-prod friendly ping for review 🙂 |
|
buildkite test this |
|
💛 Build succeeded, but was flaky
Failed CI StepsHistory
cc @kruskall |
* 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)
* 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
|
@Mergifyio backport 8.18 |
✅ Backports have been createdDetails
|
* 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
* 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>
* 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)
* 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>
* 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>





What does this PR do?
bump go to 1.24.0
Why is it important?
should help with fips among other things
Checklist
./changelog/fragmentsusing the changelog toolDisruptive User Impact
How to test this PR locally
Related issues
Questions to ask yourself