Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

promote eck 2.13 #3003

Merged
merged 4 commits into from
Jun 5, 2024
Merged

Conversation

kvalliyurnatt
Copy link
Contributor

This adds ECK 2.13 as the current branch. ECK 2.13.0 is planned for 21st May 2024, so this PR should be merged on 21st and after #3002 .

Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

conf.yaml Outdated Show resolved Hide resolved
conf.yaml Show resolved Hide resolved
@bmorelli25
Copy link
Member

Okay wait I'm confused. If both of these PRs need to be merged on the same day then we should just combine them. I don't see a benefit to merging them separately.

@kvalliyurnatt
Copy link
Contributor Author

kvalliyurnatt commented May 14, 2024

Okay wait I'm confused. If both of these PRs need to be merged on the same day then we should just combine them. I don't see a benefit to merging them separately.

my bad, #3002 will be merged one day before release, on May 20th and this on May 21st

@kvalliyurnatt kvalliyurnatt merged commit 0f47b6e into elastic:master Jun 5, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants