-
Notifications
You must be signed in to change notification settings - Fork 115
Specify more bodies as optional #5469
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
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Based on Elasticsearch YAML tests
Following you can find the validation changes against the target branch for the APIs.
You can validate these APIs yourself by using the |
l-trotta
approved these changes
Oct 13, 2025
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-8.19 8.19
# Navigate to the new working tree
cd .worktrees/backport-8.19
# Create a new branch
git switch --create backport-5469-to-8.19
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 50cdd12dd69654a6aa37ac4f48ff35100014c5b2
# Push it to GitHub
git push --set-upstream origin backport-5469-to-8.19
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.19 Then, create a pull request where the |
github-actions bot
pushed a commit
that referenced
this pull request
Oct 13, 2025
Based on Elasticsearch YAML tests (cherry picked from commit 50cdd12)
pquentin
added a commit
that referenced
this pull request
Oct 13, 2025
Based on Elasticsearch YAML tests (cherry picked from commit 50cdd12) # Conflicts: # specification/_global/search/SearchRequest.ts
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
pquentin
added a commit
that referenced
this pull request
Oct 13, 2025
pquentin
added a commit
that referenced
this pull request
Oct 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on Elasticsearch YAML tests, which found that all those APIs did not actually require a body: elastic/elasticsearch@c2035a3.