Skip to content

fix: axios version upgrade #38

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sriramveeraghanta merged 1 commit into from
Oct 13, 2025
Merged

fix: axios version upgrade #38

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 9 additions & 8 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@
"dependencies": {
"@modelcontextprotocol/sdk": "^1.9.0",
"@scarf/scarf": "^1.4.0",
"axios": "^1.8.4",
"axios": "1.12.0",

@coderabbitai coderabbitai Bot Oct 13, 2025

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Lockfile still points at the old axios version.

Pinning axios here without regenerating the repository lockfile means npm ci (and anyone else relying on the lockfile) will continue to install the previous 1.8.x release, so the upgrade never actually lands. Please rerun the appropriate install command (npm install, pnpm install, etc.) and commit the updated lockfile alongside this change.

🤖 Prompt for AI Agents 
In package.json around line 36, you pinned axios to 1.12.0 but did not
regenerate the repository lockfile, so CI and installs will still resolve the
old 1.8.x version; run the project’s package manager install command (e.g., npm
install or pnpm install) to update package-lock.json or pnpm-lock.yaml, verify
the lockfile now references axios 1.12.0, and commit the updated lockfile
alongside this package.json change.

"zod-to-json-schema": "^3.24.5"
},
"devDependencies": {
Expand Down