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
Bump axios from 0.21.1 to 0.27.2 #2286
Conversation
The following labels could not be found: |
e86fa70
to
19a6be1
Compare
19a6be1
to
0d21c51
Compare
0d21c51
to
ccd0e19
Compare
❌ Deploy Preview for care-net failed.
|
ccd0e19
to
b23efbe
Compare
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
GitGuardian id | Secret | Commit | Filename | |
---|---|---|---|---|
757392 | Google API Key | 2cec8ae | src/Common/env.tsx | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 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!
@rithviknishad Can you check the Breaking Changes between these version and see if we're good to go ahead with this? |
@dependabot rebase |
b23efbe
to
28b2410
Compare
None of the breaking changes seems to effect our usage. Tested deploy too and everything seems to work, no issues due to axios bump found yet. List of breaking changes from axios releases between the above versions
|
looks good |
@rithviknishad @gigincg is it good to be merged? |
@rithviknishad can you please take care of the merge conflict? |
28b2410
to
9411d69
Compare
@khavinshankar dependabot itself did it i guess. commenting |
Bumps [axios](https://github.com/axios/axios) from 0.21.1 to 0.27.2. - [Release notes](https://github.com/axios/axios/releases) - [Changelog](https://github.com/axios/axios/blob/master/CHANGELOG.md) - [Commits](axios/axios@v0.21.1...v0.27.2) --- updated-dependencies: - dependency-name: axios dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
9411d69
to
e682612
Compare
Bumps axios from 0.21.1 to 0.27.2.
Release notes
Sourced from axios's releases.
... (truncated)
Changelog
Sourced from axios's changelog.
... (truncated)
Commits
bc733fe
Releasing v0.27.2b9e9fb4
Enhanced protocol parsing implementation to fix #4633; (#4639)76432c1
Fixed FormData posting in browser environment by reverting #3785; (#4640)82fd15f
Combined build process and cleaned it up a bit1d82af1
Fixing issues with bundle sizesbcb166e
Fixed incorrect date in changelog838f53b
Merge branch 'master' of github.com:axios/axioscb9c534
Releasing v0.27.191d21fc
Releasing v0.72.1167cb8b
Remove eslint-g package as this seems have been added in errorMaintainer changes
This version was pushed to npm by jasonsaayman, a new releaser for axios since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)