[Snyk] Security upgrade axios from 1.7.4 to 1.13.2

[sdh100shaun]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-AXIOS-15930944	803

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

[sdh100shaun]

This upgrade of axios from 1.7.4 to 1.13.2 includes a significant breaking change for TypeScript users.

Breaking Change:

• In version 1.12.0, the type for AxiosError.cause was changed from Error to unknown. [4] Code that previously accessed properties on the cause object (e.g., error.cause.message) will now fail to compile in a strict TypeScript environment.

Recommendation:

• Action required: Before merging, you must update any error handling logic that interacts with AxiosError.cause to include a type guard or explicit type casting to safely access its properties.

While the official release notes for most minor versions in this range state there are no breaking changes, this specific type modification requires developer intervention to prevent build failures in TypeScript projects. [1, 2, 5]

Source: GitHub Issue #7059 [4], Axios v1.x CHANGELOG [1]

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.