-
Notifications
You must be signed in to change notification settings - Fork 0
[Snyk] Security upgrade axios from 0.22.0 to 1.12.0 #128
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.
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -33,7 +33,7 @@ | |
"dependencies": { | ||
"@tinyhttp/app": "^1.3.7", | ||
"apollo-server-express": "^2.25.0", | ||
"axios": "^0.22.0", | ||
"axios": "^1.12.0", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🛑 Breaking Change Risk: This upgrade spans multiple major versions (0.x to 1.x) and the PR description indicates it's a breaking change. Before merging, you should run comprehensive tests to ensure the application still functions correctly. Key areas to test include HTTP requests to the Hacker News API in the stories and user resolvers, error handling, and response data structure access patterns1. Footnotes
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Consider adding axios types to your devDependencies if they're not already included. With axios v1.x, you may want to add |
||
"body-parser": "^1.19.0", | ||
"dotenv": "^10.0.0", | ||
"graphql": "^15.5.0", | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This axios upgrade from 0.22.0 to 1.12.0 is a major version change that introduces breaking changes. The current code uses axios in several resolvers (stories.ts, user.ts) and may be affected by API changes between these versions. You should verify that the existing axios usage patterns are still compatible with v1.x, particularly around response handling and error handling.