fix(deps): clear fast-uri HIGH advisories with 4.1.4 (ports upstream #136700) - #7
Merged
Merged
Conversation
…penclaw#136700 security-fast went red on main right after the upstream sync: six fast-uri advisories (four HIGH visible to pnpm audit) published after our sync point b6306da. Upstream fixed this in 4cedaa0 ("clear fast-uri and nodemailer release gate advisories", openclaw#136700); this ports the part that applies to our tree: - pnpm-workspace.yaml override fast-uri 4.1.2 -> 4.1.4 (upstream's parent was already on 4.1.3, ours was not) - the same minimumReleaseAgeExclude cooldown entry, with upstream's removal date (2026-09-09) - lockfile regenerated with the pinned pnpm 12.0.0; the esbuild@0.28.1 entries drop out because the resolution pass collapses the duplicated esbuild onto 0.28.2, already present Not ported: the nodemailer scoped overrides (they target mailparser@3.9.15; our tree has 3.9.16, and pnpm audit reports no nodemailer HIGH here) and the vercel-cli release-gate lock refresh (release workflows only; not exercised by this fork's CI). The next upstream sync brings both verbatim. Verified: node scripts/pre-commit/pnpm-audit-prod.mjs --audit-level=high -> "No high or higher advisories found for production dependencies." Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WqKqMnHQHSmkGFfc5t7Rxn
Dependency GuardThis PR changes dependency-related files. Maintainers should confirm these changes are intentional. Changed files:
Maintainer follow-up:
|
Dependency graph changes notedThis PR includes dependency graph changes. The dependency guard is informational because the PR author is a repository admin, a member of
Security review is still recommended before merge when the dependency graph change is intentional. |
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.
security-fastwent red on main immediately after the upstream sync (#6): six fast-uri advisories (four HIGH visible topnpm audit --prod) were published after our sync pointb6306da1a9. Upstream fixed the same thing hours later in4cedaa057a(#136700); this PR ports the part that applies to our tree instead of hand-writing a divergent fix:pnpm-workspace.yaml: overridefast-uri4.1.2 → 4.1.4 + upstream'sminimumReleaseAgeExcludecooldown entry (removal date 2026-09-09, upstream's own)pnpm-lock.yaml: regenerated with the pinned pnpm 12.0.0. Theesbuild@0.28.1entries drop out because the resolution pass collapses the duplicated esbuild onto 0.28.2 (already present, all platform variants intact)Not ported (documented, deliberate): upstream's nodemailer scoped overrides (they target
mailparser@3.9.15; our tree has 3.9.16 so they would not bind, and our audit reports no nodemailer HIGH) and the vercel-cli release-gate lock refresh (release workflows only, not exercised by this fork's CI). The next upstream sync brings both verbatim.Local verification with the exact CI command:
This PR's push run also demonstrates the self-heal of
checks-fast-bundled-protocol(its diff base is now the synced tree, not the 3-month-old one).🤖 Generated with Claude Code
https://claude.ai/code/session_01WqKqMnHQHSmkGFfc5t7Rxn