Skip to content

[9.0] Backports #2618 #2620

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

Merged
merged 2 commits into from
Apr 7, 2025
Merged

[9.0] Backports #2618 #2620

merged 2 commits into from
Apr 7, 2025

Conversation

picandocodigo
Copy link
Member

No description provided.

The code is automatically generated from elasticsearch-specification:
https://github.com/elastic/elasticsearch-specification
The value Elasticsearch::ES_SPECIFICATION_COMMIT will be updated with the commit hash of
elasticsearch-specification in which the code is based.

Instead of writing the commit hash in each generated file, it will be saved in this constant.
Copy link

github-actions bot commented Apr 7, 2025

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.

@picandocodigo picandocodigo merged commit f40af02 into 9.0 Apr 7, 2025
14 checks passed
@picandocodigo picandocodigo deleted the backport_2618 branch April 7, 2025 09:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant