fix: explicitly upgrade axios to 1.7.9 [ZEND-5779] #1448
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
BobHemphill76
approved these changes
Dec 30, 2024
|
🎉 This PR is included in version 4.26.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Explicitly upgrade axios to ^1.7.9 so downstream consumers know that the latest is the acceptable valid version.
Description
Motivation and Context
Even though axios was previously bumped to 1.7.9 in the lockfile, 1.7.4 was still marked as valid for downstream consumers, so they wouldn't get the new version without regenerating their lockfile or executing npm audit fix in their projects that use contentful-migration.