[codex] fix release audit vulnerabilities#16
Merged
Conversation
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.
TL;DR
Fixed release-blocking supply-chain audit failures by upgrading Vite and pinning vulnerable transitive paths to patched versions.
What changed?
8.0.14to8.0.16undici7.x transitive pathspnpm-lock.yamlAGENTS.mdproject learning for the release-audit dependency postureHow to test?
CI=true pnpm install --frozen-lockfilepnpm audit --audit-level moderatepnpm buildpnpm testpnpm typecheckpnpm lintWhy make this change?
This clears the P0 release audit failure while preserving the repo pinned dependency style. The patched graph resolves to
vite@8.0.16andundici@7.28.0;pnpm audit --audit-level moderatepasses with only one low advisory remaining below the requested threshold.Need help on this PR? Tag
@codesmithwith what you need. Autofix is disabled.Note
Low Risk
Dev-only dependency and lockfile pinning with no runtime product code changes; main risk is minor dev/build toolchain behavior shifts from Vite and rolldown bumps.
Overview
Addresses release-blocking supply-chain audit failures by moving demo apps off vulnerable Vite 8.0.14 and forcing patched transitive versions across the lockfile.
Vite is bumped from
8.0.14to8.0.16inmf-host,mf-remote-dashboard,mf-remote-settings, andplayground. Rootpnpm-workspace.yamloverrides pin anyvite@>=8.0.0 <=8.0.15to8.0.16and anyundici@>=7.0.0 <7.28.0to7.28.0, so module-federation, Vitest, and jsdom paths resolve consistently. The lockfile refresh also pulls rolldown1.0.3as part of the Vite 8.0.16 graph.AGENTS.mddocuments keeping demo Vite at 8.0.16+ and these overrides until upstream catches up, with the expectation thatpnpm audit --audit-level moderatestays clean aside from acceptable low advisories.Reviewed by Cursor Bugbot for commit 9dfd097. Bugbot is set up for automated code reviews on this repo. Configure here.