[Snyk] Security upgrade superagent from 3.7.0 to 10.2.2

[snyk-io]

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

Snyk changed the following file(s):

• samples/client/petstore/javascript-promise/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-14724253	170

---

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

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[snyk-io]

This is a very large major version upgrade from v3 to v10, introducing significant breaking changes that require code and environment updates.

Highlights:

• Node.js Requirement: Support for older Node.js versions has been dropped. Version 9.0.0 and later require Node.js v14.18.0 or newer. [11]
• API Pattern Change: The library has fully embraced Promise-based APIs (.then()/await). The older callback-style .end() method no longer returns the request object, which will break chained calls. [7]

Source: superagent GitHub HISTORY.md
Recommendation: This upgrade requires significant code review and potential refactoring. Developers must verify their Node.js runtime version and migrate from .end() callbacks to promise-based patterns.

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