fix: axios version upgrade

[sriramveeraghanta]

Description

• Axios Version Upgrade

Type of Change

• Dependency Upgrade

Summary by CodeRabbit

• Chores
  • Locked the app’s network/HTTP client to a specific version to improve stability and reproducibility across environments.
  • Reduces risk of breaking changes from automatic dependency updates.
  • Ensures more consistent performance and compatibility during installs and builds.
  • No user-facing functionality or UI changes; existing features continue to work as before.

[coderabbitai]

Walkthrough

Pinned the axios dependency in package.json from a caret range (^1.8.4) to a fixed version (1.12.0). No other files or settings were modified.

Changes

Cohort / File(s)	Summary of Changes
Dependencies package.json	Updated dependencies.axios from ^1.8.4 to 1.12.0 (pinned version).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nibbled the vines where versions grow,
Snipped the caret—steady we go!
A fixed sip of axios tea,
Less wobble for the burrow’s CI.
Thump-thump! Release hops neat and tight,
Carrots pinned, and builds feel light. 🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title succinctly and accurately describes the primary change in the pull request by indicating an Axios version upgrade. It is concise, clear, and directly related to the modification of the dependency declaration without extraneous information. This allows reviewers to understand the main change at a glance.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch axios-version-bump

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1a199cd and c339759.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json (1 hunks)

[coderabbitai]

⚠️ 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.