Repository navigation
ci: reduce superseded validation and dependency downloads - #269
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Superseded PR heads currently finish the full validation matrix after a newer head starts. Cancel obsolete PR validation in CI, CodeQL and offline-evidence export while giving every main push, scheduled run and manual run an independent concurrency group.
Reuse pip/npm download caches keyed by the dependency manifests, bound previously unbounded jobs, and retain routine candidate-journey diagnostics for 14 days. Release artifacts, release evidence, qualification writers and protected benchmark workflows keep their existing retention and serialization. All test commands, security scans, Python/OS matrices, conditions and triggers remain intact; clean installs and independent distribution builders still execute.
Published head
0a4a89d2cae98ad023273a71c2c1b416ec7b69daincorporates qualified main4cd10f1e5e1092db74380652e5e123aa32a3ba61through an ordinary two-parent merge with no conflicts or manual resolutions. Its tree is91d4d2b3214d05a3772102a36f589c2b4c68084e. Only the five reviewed workflows differ from that primary tree; all 1,998 other tracked objects and modes, 587 official producer bindings, 700 evidence assets and 29 runtime assets are preserved. Two independent structural reviews confirmed that preservation and all allowed workflow changes. Fresh local validation on this exact head passed all 69 maintained release/workflow guards with zero failures, errors, skips or network attempts; whitespace checks passed.Fresh hosted validation on this exact head completed successfully: all 30 checks, 29 actual workflow jobs and three workflow runs passed. Python 3.10 passed 10,174 tests with 24 expected skips; Python 3.11–3.14 each passed 10,176 with 22 expected skips. The Python 3.9 NumPy-only floor passed 8,021 with 423 expected extra/platform skips, and the browser suite passed 284. The maintained Python 3.11 coverage job passed 10,176 tests with 22 skips and measured 86.63% statement coverage against its unchanged 60% gate; it does not enable branch coverage. Linux, Windows and macOS installed MCP/server journey artifacts were independently checked against their actual package/source bindings. The tested PR merge commit
c204358d4f2cc66ea4cb004893ccfea36e8c4531has parents4cd10f1e5e1092db74380652e5e123aa32a3ba61and0a4a89d2cae98ad023273a71c2c1b416ec7b69da, and exactly the qualified tree above.These are new executions for this published integration head; earlier original-cost-head and Core release results remain historical. Merge uses the repository's allowed squash method, preserving the qualified complete tree. No protection or review requirement is waived, and no direct release publication, provider or deployment action is part of this change.