chore(deps): update kibana-openapi-spec digest to 718e7a2#1402
Merged
elastic-renovate-prod[bot] merged 1 commit intomainfrom Oct 29, 2025
Merged
chore(deps): update kibana-openapi-spec digest to 718e7a2#1402elastic-renovate-prod[bot] merged 1 commit intomainfrom
elastic-renovate-prod[bot] merged 1 commit intomainfrom
Conversation
elastic-renovate-prod
bot
force-pushed
the
renovate/kibana-openapi-spec-digest
branch
from
80eae38 to
21229e9
Compare
elastic-renovate-prod
bot
changed the title
elastic-renovate-prod
bot
force-pushed
the
renovate/kibana-openapi-spec-digest
branch
from
21229e9 to
af5356b
Compare
elastic-renovate-prod
bot
changed the title
elastic-renovate-prod
bot
force-pushed
the
renovate/kibana-openapi-spec-digest
branch
from
af5356b to
037c640
Compare
elastic-renovate-prod
bot
changed the title
8 tasks
elastic-renovate-prod
bot
force-pushed
the
renovate/kibana-openapi-spec-digest
branch
from
037c640 to
59e4fe2
Compare
elastic-renovate-prod
bot
changed the title
elastic-renovate-prod
bot
force-pushed
the
renovate/kibana-openapi-spec-digest
branch
from
59e4fe2 to
8e5427e
Compare
elastic-renovate-prod
bot
changed the title
elastic-renovate-prod
bot
force-pushed
the
renovate/kibana-openapi-spec-digest
branch
from
8e5427e to
080690a
Compare
elastic-renovate-prod
bot
changed the title
elastic-renovate-prod
bot
force-pushed
the
renovate/kibana-openapi-spec-digest
branch
from
080690a to
9b946cd
Compare
elastic-renovate-prod
bot
changed the title
elastic-renovate-prod
bot
force-pushed
the
renovate/kibana-openapi-spec-digest
branch
from
9b946cd to
313ebe5
Compare
elastic-renovate-prod
bot
changed the title
elastic-renovate-prod
bot
force-pushed
the
renovate/kibana-openapi-spec-digest
branch
from
313ebe5 to
07af40d
Compare
elastic-renovate-prod
bot
changed the title
elastic-renovate-prod
bot
force-pushed
the
renovate/kibana-openapi-spec-digest
branch
from
07af40d to
994cf13
Compare
elastic-renovate-prod
bot
changed the title
elastic-renovate-prod
bot
force-pushed
the
renovate/kibana-openapi-spec-digest
branch
from
994cf13 to
a2f491b
Compare
elastic-renovate-prod
bot
changed the title
tobio
added a commit
to elastic/kibana
that referenced
this pull request
Oct 29, 2025
## Summary From #239314 (comment) the `entityID` is expected to be supplied in the request body, but the path parameter was only partially removed. This results in an invalid API specification which breaks [client generation](elastic/terraform-provider-elasticstack#1402 (comment)). ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [x] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [x] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
elastic-renovate-prod
bot
changed the title
elastic-renovate-prod
bot
force-pushed
the
renovate/kibana-openapi-spec-digest
branch
2 times, most recently
from
00cd226 to
e96fb85
Compare
elastic-renovate-prod
bot
changed the title
elastic-renovate-prod
bot
force-pushed
the
renovate/kibana-openapi-spec-digest
branch
from
e96fb85 to
b5635ca
Compare
tkajtoch
pushed a commit
to tkajtoch/kibana
that referenced
this pull request
Oct 29, 2025
## Summary From elastic#239314 (comment) the `entityID` is expected to be supplied in the request body, but the path parameter was only partially removed. This results in an invalid API specification which breaks [client generation](elastic/terraform-provider-elasticstack#1402 (comment)). ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [x] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [x] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
elastic-renovate-prod
bot
force-pushed
the
renovate/kibana-openapi-spec-digest
branch
from
b5635ca to
b793af7
Compare
elastic-renovate-prod
bot
changed the title
tobio
approved these changes
Oct 29, 2025
elastic-renovate-prod
bot
deleted the
renovate/kibana-openapi-spec-digest
branch
qn895
pushed a commit
to qn895/kibana
that referenced
this pull request
Oct 30, 2025
## Summary From elastic#239314 (comment) the `entityID` is expected to be supplied in the request body, but the path parameter was only partially removed. This results in an invalid API specification which breaks [client generation](elastic/terraform-provider-elasticstack#1402 (comment)). ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [x] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [x] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
ana-davydova
pushed a commit
to ana-davydova/kibana
that referenced
this pull request
Nov 3, 2025
## Summary From elastic#239314 (comment) the `entityID` is expected to be supplied in the request body, but the path parameter was only partially removed. This results in an invalid API specification which breaks [client generation](elastic/terraform-provider-elasticstack#1402 (comment)). ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [x] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [x] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
albertoblaz
pushed a commit
to albertoblaz/kibana
that referenced
this pull request
Nov 4, 2025
## Summary From elastic#239314 (comment) the `entityID` is expected to be supplied in the request body, but the path parameter was only partially removed. This results in an invalid API specification which breaks [client generation](elastic/terraform-provider-elasticstack#1402 (comment)). ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [x] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [x] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR contains the following updates:
9d23eeb->718e7a2Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.