chore(ci): bump rstack-ecosystem-ci dispatch action to latest main#14726
chore(ci): bump rstack-ecosystem-ci dispatch action to latest main#14726stormslowly wants to merge 1 commit into
Conversation
|
cannot determine workflow run id |
There was a problem hiding this comment.
Pull request overview
This PR updates the pinned commit SHAs for the external rstackjs/rstack-ecosystem-ci GitHub Actions used to trigger Ecosystem CI, moving from the previously tagged v0.3.4 commit to a newer commit on main in order to exercise the updated JS-based workflow_dispatch implementation end-to-end.
Changes:
- Bump
ecosystem_ci_dispatchaction reference inecosystem-ci.ymltoedf483f3a550a8257aab674f076879b23047f350. - Bump
ecosystem_ci_per_commitaction reference inci.ymltoedf483f3a550a8257aab674f076879b23047f350.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/workflows/ecosystem-ci.yml | Updates the pinned SHA for the PR-triggered Ecosystem CI dispatch action. |
| .github/workflows/ci.yml | Updates the pinned SHA for the per-commit Ecosystem CI trigger action. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Merging this PR will not alter performance
Comparing Footnotes
|
Why
rstack-ecosystem-ci#64swapped the Docker-basedtrigger-workflow-and-waitfor a JSworkflow_dispatchimplementation in the dispatch action. That change is onmainbut not yet tagged, so our pinnedv0.3.4(ecca2c8) still runs the old Docker path.This bumps both eco-CI action references to the latest
mainhash (edf483f3) so we exercise the new JS dispatch end-to-end.ci.yml(ecosystem_ci_per_commit)ecca2c8v0.3.4edf483f3main #64ecosystem-ci.yml(ecosystem_ci_dispatch)ecca2c8v0.3.4edf483f3main #64