[Chore] Update safe workspace dependencies - #1346
Draft
roomote-management[bot] wants to merge 1 commit into
Draft
roomote-management[bot] wants to merge 1 commit into
roomote-management[bot] wants to merge 1 commit into
Conversation
✅ Deploy Preview for starter-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for shopify-next-tailwind canceled.
|
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.
What changed
simple-gitto3.36.0to clear its RCE advisories.minimatchandbrace-expansionchains onto patched releases.serverless-esbuildto1.52.1and Tailwind CSS to3.4.17, the newest tested releases that preserve the repository's Node 14/16 support.Why this change was made
The workspace had 26 audit findings and a broad set of stale compatible dependencies. This update takes the safe maintenance improvements while avoiding dependency lines that silently raise the repository's runtime requirement to Node 18 or 20.
Impact
There is no intended product behavior change. On Node 16.20.2, the frozen install, lint, CLI build, 100-route website build, and metrics packaging all pass; the website also renders successfully in a browser. The audit is reduced from 26 findings to 15.
The remaining security fixes are deferred because they require a runtime migration:
tiged -> tar: moving fromtar@6to patchedtar@7.5.22requires Node 18 and should be handled with the repository's Node support policy and CLI compatibility review. This accounts for 13 remaining findings.autoprefixer -> browserslist: patchedbrowserslist@4.28.7resolves to anode-releasesline requiring Node 18. This accounts for 2 remaining findings.Other deferred major upgrades:
react-lottie-player1 to 2 require application compatibility testing.yargs-parser21 to 22,clsx1 to 2,prettier-plugin-astro0 to 1, and newer esbuild lines require API or tooling migration checks.Screenshots