Repository navigation
chore(deps): bump next in realtime-js example to fix pnpm audit - #2787
Conversation
Resolves GHSA-2464-fhr4-w9xw, GHSA-673q-mjm6-r5xr and GHSA-p3m5-59mp-jv5r (next >=16.0.0 <=16.4.0), which fail the production audit step in ci-core. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Summary
Priority: ⬆️ High Change: Other Merge Risk: ⚪ Minimal · up to
|
@supabase/auth-js
@supabase/functions-js
@supabase/postgrest-js
@supabase/realtime-js
@supabase/storage-js
@supabase/supabase-js
commit: |

🔍 Description
What changed?
nextinpackages/core/realtime-js/examplefrom^16.3.8to^16.4.1(lockfile resolves16.4.2).Why was this change needed?
pnpm audit --audit-level=high --prodinci-corenow fails on threenextadvisories (>=16.0.0 <=16.4.0, fixed in>=16.4.1):The only path is
packages__core__realtime-js__example>next. The example app is private and not published, so no consumer is exposed, but the audit step blocks every PR and Dependabot update until it is fixed. After this lands, blocked PRs need a rebase onto master.🔄 Breaking changes
📋 Checklist
<type>(<scope>): <description>pnpm nx formatto ensure consistent code formatting📝 Additional notes
Verified locally:
pnpm audit --audit-level=high --prod --registry https://registry.npmjs.orgreports no known vulnerabilities after the bump. I did not run the example app's Playwright tests ornext build; CI will cover those.🤖 Generated with Claude Code