Skip to content
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

[Snyk] Upgrade axios from 1.1.3 to 1.2.0 #124

Merged
merged 2 commits into from
Feb 2, 2023

Conversation

maidul98
Copy link
Collaborator

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade axios from 1.1.3 to 1.2.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 2 versions ahead of your current version.
  • The recommended version was released 22 days ago, on 2022-11-22.
Release notes
Package name: axios from axios GitHub release notes
Commit messages
Package name: axios
  • f92e167 chore(release): 1.2.0
  • bc09c90 chore(docs): updated changelog
  • d032edd Refactored adapters loader; (#5277)
  • a3d9017 Fixed Z_BUF_ERROR when content-encoding is set but the response body is empty; (#5250)
  • b7ee49f Added toJSONObject util; (#5247)
  • a372b4c update readme (#5261)
  • e05fe7c Update the link (#5265)
  • 7a4c0ea __dirname is not defined (#5269)
  • 86eeff0 ci: remove git credentials after checkout (#5235)
  • 2c83d47 chore(deps): bump loader-utils from 1.4.1 to 1.4.2 (#5295)
  • f79cf7b chore(deps): bump actions/dependency-review-action from 2 to 3 (#5266)
  • e1989e9 chore(deps): bump engine.io from 6.2.0 to 6.2.1 (#5294)
  • 3a7c363 chore: v1.2.0 pre-release
  • bb59a73 chore: release v1.2.0
  • 073f727 chore: updated release notes
  • 4d43cdb chore: switch around order of changelog
  • abf9541 fix: fix TypeScript type definitions for commonjs (#5196)
  • 7f0fc69 chore(deps): bump loader-utils from 1.4.0 to 1.4.1 (#5245)
  • 0da6db7 chore(deps): bump socket.io-parser from 4.0.4 to 4.0.5 (#5241)
  • ab77a40 Fixed & Imporoved AxiosHeaders class (#5224)
  • c0a723a Added support for Axios to be loaded with require('axios').default; (#5225)
  • 9452f06 Force CI restart;
  • 56fd6ba Remove `\b` from filename (#5207)
  • 7c4e4fd fix punctation in README.md (#5197)

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@gitguardian
Copy link

gitguardian bot commented Feb 2, 2023

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id Secret Commit Filename
5324534 Generic High Entropy Secret ea0fe1b .env.example View secret
5324535 Generic High Entropy Secret ea0fe1b .env.example View secret
5324536 Generic High Entropy Secret ea0fe1b .env.example View secret
5324537 Generic High Entropy Secret ea0fe1b .env.example View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!

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