Repository navigation
chore(deps): security bumps 2026-10-06 - #6873
Conversation
|
I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".
|
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.
🟢 Approval recommended
The focused lockfile update is valid, compatible with PostCSS’s dependency range, and uses verified package metadata.
Copilot wasn't able to review any files in this pull request.
Files not reviewed (1)
- web/package-lock.json: Generated file
…work All three changed source-map-js fields already equal current main at1.2.2, carried by9e68c17a4e. An independent three-way merge is conflict-free and produces the exact current-main tree. 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 #6873 Signed-off-by: CodeWhale Bot <bot@codewhale.net>
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.
The original source-map-js 1.2.1 → 1.2.2 fix is already carried by 9e68c17a4e. Every changed version, tarball and integrity field matches current main.
The original PR commits remain ancestors of the updated source branch. Reconciliation head
a6d926c05c8513b3059495b32d09aca4642d910fmerges 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
29f71aba0e04f81402f7018b7af3b9104b985bc5; source branch and authored history are preserved. Resulting-main checks remain separate.0.10.2 has not been published. Source branches are preserved.