[codex] Fix high severity dependency alerts#18167
Merged
caseysilver-oai merged 1 commit intomainfrom Apr 20, 2026
Merged
Conversation
Contributor
|
All contributors have signed the CLA ✍️ ✅ |
Contributor
Author
|
I have read the CLA Document and I hereby sign the CLA |
rreichel3-oai
approved these changes
Apr 16, 2026
Contributor
rreichel3-oai
left a comment
There was a problem hiding this comment.
Thanks for doing this!
| "minimatch@3.1.2": "3.1.4", | ||
| "minimatch@9.0.5": "9.0.7", | ||
| "path-to-regexp": "8.4.0", | ||
| "picomatch@2.3.1": "2.3.2", |
Contributor
There was a problem hiding this comment.
Any idea why we needed to add these to package.json for this bump?
Contributor
Author
There was a problem hiding this comment.
Most of these are transitive deps so we need to force the resolution to fix versions
dylan-hurd-oai
approved these changes
Apr 20, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
resolutionsmechanism so the lockfile moves only to patched versions.pnpm-lock.yamlfor@modelcontextprotocol/sdk,handlebars,path-to-regexp,picomatch,minimatch,flatted,rollup, andglob.quinn-protofrom0.11.13to0.11.14and refreshMODULE.bazel.lock.Testing
corepack pnpm --store-dir .pnpm-store install --frozen-lockfile --ignore-scriptscorepack pnpm audit --audit-level high(passes; remaining advisories are low/moderate)corepack pnpm -r --filter ./sdk/typescript run buildcorepack pnpm exec eslint 'src/**/*.ts' 'tests/**/*.ts'cargo check --lockedcargo build -p codex-clibazel --output_user_root=/tmp/bazel-codex-dependabot --ignore_all_rc_files mod deps --lockfile_mode=errorjust fmtNote:
corepack pnpm -r --filter ./sdk/typescript run testwas also attempted after buildingcodex; it is blocked on this workstation by host-managed Codex MDM/auth state (approval_policyrestrictions and ChatGPT/API-key mismatch), not by this dependency change.