fix: update next and postcss security deps#80
Draft
dannyneira wants to merge 1 commit into
Draft
Conversation
Co-Authored-By: Oz <oz-agent@warp.dev>
Code ReviewPR: fix: update next and postcss security deps by @dannyneira
Wallet: Code review |
1 similar comment
Code ReviewPR: fix: update next and postcss security deps by @dannyneira
Wallet: Code review |
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
nextfrom16.2.0to16.2.6to resolve the current batch of Next.js Dependabot alerts.eslint-config-nextto16.2.6to keep the Next.js tooling version aligned.postcssto8.5.10and adds an npmoverrides.postcsspin to force Next's nestedpostcss@8.4.31dependency to the patched8.5.10release.tsconfig.jsonadjustment frommoduleResolution: "node"to"bundler"after running the upgraded build.Resolved Dependabot alerts
nextGHSA-q4gf-8mx6-v5v3nextGHSA-q4gf-8mx6-v5v3nextGHSA-8h8q-6873-q5fjnextGHSA-8h8q-6873-q5fjnextCVE-2026-44573nextCVE-2026-44573nextCVE-2026-44575nextCVE-2026-44575nextCVE-2026-45109nextCVE-2026-45109nextCVE-2026-44574nextCVE-2026-44574nextCVE-2026-44578nextCVE-2026-44578nextCVE-2026-44579nextCVE-2026-44579postcssCVE-2026-41305nextCVE-2026-44580nextCVE-2026-44580nextCVE-2026-44576nextCVE-2026-44576nextCVE-2026-44577nextCVE-2026-44577nextCVE-2026-44572nextCVE-2026-44572nextCVE-2026-44582nextCVE-2026-44582nextCVE-2026-44581nextCVE-2026-44581Verification
npm audit --jsonno longer reportsnextorpostcssadvisories after the update and override. Remaining audit entries are unrelated:brace-expansion,picomatch, andyaml.npm run lintnpx tsc lib/*.tsNEXT_PUBLIC_ALGOLIA_APP_ID=dummy NEXT_PUBLIC_ALGOLIA_SEARCH_API_KEY=dummy npx next buildNote:
npm run buildreaches the Algoliapostbuildpublishing step and fails in this sandbox when using dummy Algolia credentials, so the compile path was validated directly without publishing search data.Conversation: https://staging.warp.dev/conversation/ab7292d2-cf6e-4f63-a336-17845f66438d
Run: https://oz.staging.warp.dev/runs/019e3184-1bb8-759c-9558-dc9283e4ea69
This PR was generated with Oz.