golang 1.22.1

[v1v]

Proposed commit message

• WHAT: Use golang 1.22.1
• WHY: 1.22.1 has been released and https://github.com/elastic/golang-crossbuild/releases/tag/v1.22.1 is available now

Checklist

• 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.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

[botelastic]

This pull request doesn't have a Team:<team> label.

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @v1v? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[v1v]

/package

[elasticmachine]

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 135 min 26 sec

Pipeline error

This error is likely related to the pipeline itself. Click here
and then you will see the error (either incorrect syntax or an invalid configuration).

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: c9352c0

Failed CI Steps

• :linux: Unit Tests / family/core-rhel-9

History

• 💚 Build #2186 succeeded 52d50eb
• 💚 Build #2157 succeeded 2bb32be

cc @v1v

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: c9352c0

Failed CI Steps

• :rhel: RHEL-9 Unit Tests

History

• 💚 Build #1897 succeeded 52d50eb
• 💚 Build #1868 succeeded 2bb32be

cc @v1v

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: c9352c0

Failed CI Steps

• :linux: Ubuntu Unit Tests
• :go: Go Integration Tests

History

• 💔 Build #1890 failed 52d50eb
• 💔 Build #1861 failed 2bb32be

cc @v1v

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: c9352c0

History

• 💚 Build #1053 succeeded 52d50eb
• 💚 Build #1024 succeeded 2bb32be

cc @v1v

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: c9352c0

History

• 💚 Build #3104 succeeded 52d50eb
• 💚 Build #3075 succeeded 2bb32be

cc @v1v

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: c9352c0

History

• 💚 Build #3527 succeeded 52d50eb
• 💚 Build #3499 succeeded 2bb32be

cc @v1v

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b feature/bump-version-1.22.1 upstream/feature/bump-version-1.22.1
git merge upstream/main
git push upstream feature/bump-version-1.22.1