fix(ASEC-506): Snyk has created this PR to upgrade axios from 0.24.0 to 1.13.5.#14
Open
Epic-Snykie wants to merge 1 commit intomainfrom
Open
fix(ASEC-506): Snyk has created this PR to upgrade axios from 0.24.0 to 1.13.5.#14Epic-Snykie wants to merge 1 commit intomainfrom
Epic-Snykie wants to merge 1 commit intomainfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
PRs / Design Documents / Other documentation:
https://epidemicsound.atlassian.net/wiki/spaces/SEC/pages/3399155762/Snyk+Developer+Guide#Epic-Snykie-bot
What
This PR has been opened to make sure our repositories are kept up-to-date. It updates axios from version 0.24.0 to version 1.13.5 due to found vulnerabilities in the previous package version. To find more details, see the Snyk project
The PR will fix 3 issues. Changes included in this PR:
backend/package.json,backend/package-lock.json
If the PR deemed to be not a low risk one and required additional testing, add a reference to the actual upgrade ticket created for it
How has this been tested?
The PR has been open automatically and has not been tested
Rollback
Revert the PR