yuqi1129 opened a new pull request, #14276: URL: https://github.com/apache/gravitino/pull/14276
### What changes were proposed in this pull request? Validate Fork CI caller jobs against `required_ci.needs` from the immutable, trusted workflow version: the matching PR base snapshot for ordinary runs, or the upstream dispatch commit for trusted runs. Share workflow contents reads with migration detection and retain the existing execution, context and trust checks. Also require trusted verification when changed CI definitions report only a fail-fast watcher failure. ### Why are the changes needed? The publisher currently applies the latest hard-coded suite list to historical runs. Adding TMS on main therefore changed PR #14197's successful Fork CI run into an error, even though that run's workflow did not contain TMS. Re-running the same old workflow cannot satisfy the newer list. Related to #14197. ### Does this PR introduce _any_ user-facing change? Historical successful Fork CI runs keep their correct status when required callers change on main. No application API or configuration changes. ### How was this patch tested? - `node --test .github/scripts/tests/*.test.cjs`: 103 tests passed. - Regression tests cover added/removed callers, ordinary versus trusted definition snapshots, a newer tested merge base, malformed workflow contents, API failures, shared reads, recovery from transient lookup failures across polling passes, and the changed-definition watcher-only path. - The six initial regression tests fail against the original implementation. An independent mutation check also confirms the snapshot regressions detect use of the latest suite list. - Replayed PR #14197's actual run/job metadata with its historical workflow: the latest list reports missing TMS; the matching historical list reports success. - `node --check` for changed scripts and `git diff --check` passed. No live commit statuses were modified during validation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
