You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The orchestrator workspace still pulls in axios@1.13.2 via @openapitools/openapi-generator-cli even
after bumping direct deps to ^1.15.0, so installs still include an older axios version. This
undermines the stated goal of updating axios for CVE remediation and may keep vulnerability scanners
failing.
ⓘ Recommendations generated based on similar findings in past PRs
Evidence
The changeset explicitly states this change is for an axios CVE update. However, in the orchestrator
workspace lockfile, @openapitools/openapi-generator-cli is pinned to axios 1.13.2, and yarn.lock
contains both axios 1.13.2 and 1.15.0 entries—meaning the workspace still installs the older axios
version.
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution
## Issue description
This PR bumps direct axios dependencies to `^1.15.0`, but `workspaces/orchestrator/yarn.lock` still installs `axios@1.13.2` via `@openapitools/openapi-generator-cli`. As a result, the orchestrator workspace still contains an older axios version even after this update.
## Issue Context
- `@openapitools/openapi-generator-cli@2.25.2` is a devDependency and is locked to `axios: 1.13.2` in the workspace lockfile.
- The changeset message indicates the intent is CVE remediation.
## Fix Focus Areas
- Update the devDependency that pins axios, and/or force a workspace-wide axios version:
- workspaces/orchestrator/plugins/orchestrator-common/package.json[64-70]
- workspaces/orchestrator/package.json[52-60]
- Regenerate the lockfile after the dependency/resolution change:
- workspaces/orchestrator/yarn.lock[9993-10002]
- workspaces/orchestrator/yarn.lock[17815-17835]
## Suggested approaches
1) Preferably bump `@openapitools/openapi-generator-cli` to a version that depends on a non-vulnerable axios.
2) If upgrading isn’t feasible, add a `resolutions` entry for `axios` in `workspaces/orchestrator/package.json` to enforce `axios@^1.15.0`, then run `yarn --cwd workspaces/orchestrator install` (and commit the updated `yarn.lock`).
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
ⓘ The new review experience is currently in Beta. Learn more
• Created new changeset file documenting the axios security fix
• Marks patch version updates for three orchestrator packages
• References CVE-2026-40175 vulnerability
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
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.
Hey, I just made a Pull Request!
This is the manual cherry-pick of #2767
✔️ Checklist