[Chore] Dispatch snapshot releases directly#9782
Merged
weronikaolejniczak merged 5 commits intoJul 13, 2026
Merged
Conversation
weronikaolejniczak
added
skip-changelog
weronikaolejniczak
force-pushed
the
chore/dispatch-snapshot-releases-directly
branch
from
8d23feb to
4dd2682
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the EUI → Kibana regression integration pipeline to dispatch snapshot publishing via workflow_dispatch (instead of workflow_call), keeping release.yml as the top-level npm trusted publishing entry point and then continuing the Kibana dependency update chain after publish metadata exists.
Changes:
- Reworked
update_kibana_dependencies.ymlto dispatchrelease.ymlfor snapshot publishing and pass Kibana integration inputs through that workflow. - Updated
release.ymlto optionally dispatch the Kibana integration workflow chain after a successful snapshot publish. - Removed
workflow_calldefinitions from the Kibana sub-workflows, standardizing onworkflow_dispatch.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| .github/workflows/update_kibana_dependencies.yml | Switches from reusable workflow calling to dispatching release.yml for snapshot publishing + Kibana integration inputs. |
| .github/workflows/update_kibana_dependencies__prepare_changes.yml | Aligns with dispatch-based chaining and improves dispatch argument handling for optional numeric inputs. |
| .github/workflows/update_kibana_dependencies__open_pr.yml | Removes workflow_call interface, leaving this workflow dispatch-only. |
| .github/workflows/release.yml | Adds Kibana integration inputs and dispatches the Kibana workflow chain after snapshot publish metadata is available. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
mgadewoll
reviewed
Jul 10, 2026
mgadewoll
approved these changes
Jul 10, 2026
mgadewoll
left a comment
mgadewoll
left a comment
Contributor
There was a problem hiding this comment.
🟢 LGTM. I have only one non-blocking question.
In any case, we can merge and test once it's in main 👍
20 tasks
4 tasks
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
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.
Summary
Closes https://github.com/elastic/eui-private/issues/719
This PR is infra-only.
Specifically, it rewrites the Kibana regression testing pipeline from
workflow_call(so called "reusable workflows" not supported by npm trusted publishing) toworkflow_dispatch.QA instructions for reviewer
No way to test this until it lands in
main. Ensure statically the file changes make sense.