Skip to content

build(deps): update vulnerable dependency versions - #428

Open
mimiflynn wants to merge 4 commits into
mainfrom
agents/addressing-security-vulnerabilities
Open

mimiflynn wants to merge 4 commits into
mainfrom
agents/addressing-security-vulnerabilities

Conversation

@mimiflynn

Copy link
Copy Markdown
Member

Refresh the root package and site theme dependency set to remove known advisories and keep the test suite green.

Refresh the root package and site theme dependency set to remove known advisories and keep the test suite green.
mimiflynn and others added 3 commits August 19, 2026 16:15
Add npm overrides to site/package.json to force patched versions of transitive dependencies with known advisories (immutable, lodash, cookie, path-to-regexp, serialize-javascript, sharp, tmp, uuid, webpack, @parcel/reporter-dev-server, file-type). npm audit --prefix site now reports 0 vulnerabilities.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…porter-dev-server

file-type >=18 is ESM-only and breaks Gatsby's CJS require. @parcel/reporter-dev-server must match the Parcel core version bundled with Gatsby (2.8.x); overriding it to ^2.16.4 causes a version mismatch error at build time. Both overrides are removed so the site build succeeds. These two packages remain at their Gatsby-pinned versions (dev-only tooling, not runtime exposure).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Align site/package.json overrides with the sibling Crossroads repo pattern, adding js-yaml, picomatch, qs, ws, yaml. Exclude @parcel/core, @parcel/reporter-dev-server, @parcel/transformer-js and file-type overrides as they break the Gatsby build: upgrading Parcel packages beyond 2.8.3 causes a version mismatch in gatsby-parcel-config and @parcel/transformer-js hangs the compile step. These two advisories are Gatsby build-tooling only (not shipped to end users) and have no compatible patched version.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant