Conversation
🧹 chore(deps): Merge Develop Dependency Upgrades Into Main
chore(release): promote develop to main (1.0.0-beta.1)
chore(release): promote develop to main (1.0.0-beta.2)
chore(release): promote develop to main (1.0.0-beta.3)
fix(deps): patch npm audit findings and fix pp-dev bump workflow auth
chore(deps): bump next 16.2.12 and refresh lockfile to latest in-range versions
…pendabot bumps Bump postcss override and @metricinsights/pp-dev to pull in patched nanoid, fixing the two high-severity npm audit findings. Port the currently-safe Dependabot bumps (next/eslint-config-next 16.3.0, semantic-release 25.0.9, @semantic-release/git 11.0.1, @semantic-release/changelog 7.0.0, @typescript-eslint/* 8.67.0, typescript 7.0.2 in template-vanilla) directly into this branch instead of merging each PR separately. Remaining 5 moderate findings (tar/undici) come from bundleDependencies inside the npm package itself (npm@12.0.2, already latest) and can't be reached via package.json overrides. The typescript 7.0.2 bump is held back for template-nextjs, template-nextjs-esm, template-react and template-vanilla-ts because @typescript-eslint has no TS7 support yet.
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Summary
npm auditfindings (nanoid via postcss/vite) by bumping thepostcssoverride to^8.5.26and@metricinsights/pp-devto the latest1.2.2.next/eslint-config-next16.2.12 → 16.3.0 (template-nextjs, template-nextjs-esm)semantic-release25.0.8 → 25.0.9@semantic-release/git10.0.1 → 11.0.1@semantic-release/changelog6.0.3 → 7.0.0@typescript-eslint/eslint-plugin/@typescript-eslint/parser→ 8.67.0typescript6.0.3 → 7.0.2 in template-vanilla onlyRemaining audit findings (not fixable here)
5 moderate findings remain (
tar,undici, and theirnpm/@semantic-release/npm/semantic-releasechain). They come frombundleDependenciesshipped inside thenpmpackage itself (npm@12.0.2, already the latest release) — bundled deps are extracted verbatim from the tarball, so package.jsonoverridescan't reach them. This is a dev-only dependency (used by thereleasescript), not shipped to consumers. Will need an upstream npm CLI release with updated bundled deps.Held back
The
typescript7.0.2 bump is not applied to template-nextjs, template-nextjs-esm, template-react, or template-vanilla-ts. Their Dependabot PRs (#205, #202, #199, #200) fail CI with an ERESOLVE conflict —@typescript-eslint/parser/eslint-plugin, even at latest (8.67.x), still pinpeerDependencies.typescript: ">=4.8.4 <6.1.0". TypeScript 7 isn't supported by typescript-eslint yet, so those 4 PRs are left open/untouched pending upstream support.Testing
npm run typecheck✅npm run lint✅npm run build✅npm test— full scaffold suite, 19/19 passing ✅Merge Request:
origin/pp-3989→origin/develop