Skip to content

Address NPM vulnerabilities#349

Closed
leandrumartin wants to merge 2 commits intomainfrom
upgrade-follow-redirects
Closed

Address NPM vulnerabilities#349
leandrumartin wants to merge 2 commits intomainfrom
upgrade-follow-redirects

Conversation

@leandrumartin
Copy link
Copy Markdown
Collaborator

Pull Request Summary

A brief description/summary of your PR here. What does it add? Why is it necessary? How was the change made, and how was it tested?

  • Addresses Dependabot alerts about follow-redirects version number needing to be bumped up to >=16.0.0
  • Ran npm audit fix to address other issues

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot wasn't able to review any files in this pull request.

Files not reviewed (1)
  • boneset-api/package-lock.json: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

"license": "MIT",
"dependencies": {
"follow-redirects": "^1.15.11",
"follow-redirects": ">= 1.16.0",
Copy link

Copilot AI Apr 15, 2026

Choose a reason for hiding this comment

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

The lockfile now records axios as depending on follow-redirects with the range >= 1.16.0. Since this is generated from axios’s published package metadata (and previously was ^1.15.11), changing it in the lockfile can make the lock inconsistent and also allows future major versions of follow-redirects. Prefer keeping the dependency range as published (or upgrading axios) and, if the goal is to force a patched follow-redirects, add a top-level overrides/resolutions and regenerate the lockfile.

Suggested change
"follow-redirects": ">= 1.16.0",
"follow-redirects": "^1.15.11",

Copilot uses AI. Check for mistakes.
@leandrumartin leandrumartin deleted the upgrade-follow-redirects branch April 15, 2026 19:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants