Repository navigation
chore(deps): upgrade Next.js 16.2.4 → 16.3.8 and refresh vulnerable transitives - #1
Merged
Merged
Conversation
…transitives next 16.2.4 was in the range of a critical advisory (9.3.4 - 16.3.5). eslint-config-next moved with it. `npm audit fix` (no --force) then refreshed transitive dev dependencies within their existing semver ranges: 54 -> 38 advisories, 1 critical + 14 high -> 0 critical + 6 high. What remains is in eslint-config-next's own dependency chain and in @tiptap/core, which have no fixed release yet. Verified locally: lint, typecheck, 24 unit tests, next build. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
@tiptap/core <= 3.30.4 carries a high advisory; `npm update` would not move it because every @tiptap package pins core to its own version, so all 13 are bumped together. All 32 moderate advisories (the tiptap extensions) go with it: audit is now 5 high, all in eslint-config-next's dev-only dependency chain. Verified: lint, typecheck, 24 unit tests, next build. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Both e2e tests have failed on main since 2026-05-13: the sign-in/sign-up
tabs and the form's submit button share a label, so getByRole('button')
hit Playwright's strict-mode violation.
- auth-form: the switcher is role="tablist" with role="tab" and
aria-selected on each tab (also the right semantics for screen readers).
- spec: select tabs by role, assert aria-selected instead of a Tailwind
class, and scope the submit button to the form.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This branch was successfully deployed
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.
למה
next@16.2.4נמצא בטווח של advisory קריטי (9.3.4 עד 16.3.5). המאגר ציבורי.מה השתנה (2 קומיטים)
nextו-eslint-config-next: 16.2.4 → 16.3.8 (נעוץ, כמו קודם), ו-npm audit fixרגיל (בלי--force) לתלויות עקיפות.@tiptap/*: 3.23.4 → 3.31.4.@tiptap/core≤3.30.4 עם advisory גבוה, ו-npm updateלא הזיז אותו כי כל חבילת tiptap נועצת את core לגרסה שלה, אז כולן עולות יחד.npm audit
5 הנותרים הם שרשרת התלויות של
eslint-config-nextעצמו (micromatch,braces,fast-glob), כלי פיתוח בלבד, בלי גרסה מתוקנת בטווח.אימות מקומי (אחרי שני הקומיטים)
npm run lint✅npm run typecheck✅npm test: 24/24 ✅npm run build✅ (עם ערכי Supabase דמה)ה-CI יריץ את כל אלה שוב, כולל Playwright.
🤖 Generated with Claude Code