Repository navigation
chore(deps): security bumps 2026-10-08 - #6917
Conversation
|
I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".
|
…work All40 changed lockfile fields and the single Next manifest constraint are superseded by coherent16.4.0 in current main, carried byb5359077c6 and84debda8c4. Resolve the two package-file conflicts with current main verbatim, preserving newer packages and security work. Retain the original authored commit as first parent and current main as second parent. The resolved tree is exactly 89d1b98, identical to main 68f4dd3; no package downgrade or product-source change. Verified full original diff, all reviews, exact package fields, carrying ancestry and merge result. Fresh resulting-head checks remain pending; historical CI failures are not relabeled. Canonical checkout and peer native build inputs remain unchanged. Refs #6917 Signed-off-by: CodeWhale Bot <bot@codewhale.net>
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
If your organization's extra usage balance is empty, an organization admin can add extra usage credits at claude.ai/admin-settings/usage. If its monthly spend limit was reached, an admin can raise it on the same page. If neither applies, contact Anthropic support.
Once extra usage is available, someone with write access to this repository can comment @claude review on this pull request to trigger a review.
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request. Check if the Files changed in this pull request are included in default exclusions.
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. |
The original Next 16.3.6 → 16.3.8 security update is superseded by the coherent 16.4.0 packages and root constraints carried by b5359077c6 and 84debda8c4. All 40 lockfile fields and the one manifest constraint were compared; current versions are preserved.
The original PR commits remain ancestors of the updated source branch. Reconciliation head
d0e26b471d3eec678b66b9e16a1a726770632fe2merges main68f4dd34065eac930565b7e87dfb71d134fe646ewithout changing its product source: the complete resulting tree is exactly89d1b981df62ff3f625fb9fa685821f5b90a9136, identical to that main commit. This lets the original PR land with its authored history and current implementations intact.Verification: full original diff and review-thread audit, carrying ancestry, field/control-path comparison, and exact complete-tree equality pass. All exact-head checks completed successfully, including CodeQL. Older failed CI remains failed; it is not evidence for this head. A successful native job that skips work for an empty source diff is not a new native test run. Merged as this original PR in
266ec374a3684e95fcb96580772ec83efa1628fc; source branch and authored history are preserved. Resulting-main checks remain separate.0.10.2 has not been published. Source branches are preserved.