fix(deps): move Tiptap to 3.31.3 and clear the ReDoS and provider-utils advisories - #255
Merged
Merged
Conversation
…ls advisories npm audit (the first step of prod:gate) began failing on every PR: GHSA-j95f-988m-3j2f (quadratic ReDoS in Tiptap Markdown attribute parsing, fixed in 3.30.5) reached all 30 @tiptap packages pinned at ^3.30.4, and GHSA-866g-f22w-33x8 (uncontrolled resource consumption in @ai-sdk/provider-utils < 4.0.33) reached the ai-sdk providers. Tiptap packages pin exact peer versions among themselves, so the whole family moves together to 3.31.3; the ai-sdk providers move within their existing caret ranges. npm audit --omit=dev now reports 0 vulnerabilities; npm ls shows no invalid peers. Local floor: root and Convex typechecks clean; vitest 2779/2780 in the full run with one temp-directory flake in spreadsheetBenchRunner that passes 29/29 in isolation. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Scaffold Handoff — For Your Coding Agent
Immutability CheckMode: advisory ✅ No immutable files were modified in this branch. Changed Files
Needs Adversarial Review — Do NOT Apply YetThese proposals passed the reject check but have not been approved by
Safety Boundary
Immutable files (never modify):
Scaffold files (safe to modify):
|
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.
Every NodeRoom PR now fails the production gate at its first step,
npm audit --omit=dev --audit-level=moderate, because two advisories were published after main's last green run on 2026-09-05: GHSA-j95f-988m-3j2f (quadratic ReDoS in Tiptap's Markdown attribute parsing, fixed in 3.30.5) hits all 30@tiptap/*packages pinned at^3.30.4, and GHSA-866g-f22w-33x8 (@ai-sdk/provider-utils< 4.0.33) hits the ai-sdk providers. Seen first on #254's verify job (run 34578853729: 35 vulnerabilities, 29 high).Tiptap packages pin exact peer versions among themselves, so the family has to move together: all six direct pins go to
^3.31.3and the lockfile resolves the 30 packages at 3.31.3 with no invalid peers. The ai-sdk providers move within their existing caret ranges vianpm audit fix. Result:npm audit --omit=devreports 0 vulnerabilities.Local floor: root and Convex typechecks clean; vitest 2779/2780 on the full run, with one temp-directory flake in
spreadsheetBenchRunner.test.tsthat passes 29/29 in isolation. The editor surfaces get their real check from this PR's CI (prod:gate, proofloop-gate, packed consumer).🤖 Generated with Claude Code