Update axios 1.6.0 → 1.6.2 (patch)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ axios (1.6.0 → 1.6.2) · Repo · Changelog

Release Notes

1.6.2

Release notes:

Features

• withXSRFToken: added withXSRFToken option as a workaround to achieve the old withCredentials behavior; (#6046) (cff9967)

PRs

• feat(withXSRFToken): added withXSRFToken option as a workaround to achieve the old `withCredentials` behavior; ( #6046 )

📢 This PR added 'withXSRFToken' option as a replacement for old withCredentials behaviour. 
You should now use withXSRFToken along with withCredential to get the old behavior.
This functionality is considered as a fix.

Contributors to this release

• Dmitriy Mozgovoy
• Ng Choon Khon (CK)
• Muhammad Noman

1.6.1

Release notes:

Bug Fixes

• formdata: fixed content-type header normalization for non-standard browser environments; (#6056) (dd465ab)
• platform: fixed emulated browser detection in node.js environment; (#6055) (3dc8369)

Contributors to this release

• Dmitriy Mozgovoy
• Fabian Meyer

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 16 commits:

• chore(release): v1.6.2 (#6082)
• chore(ci): removed redundant release action; (#6081)
• chore(docs): fix outdated grunt to npm scripts (#6073)
• chore(docs): update README.md (#6048)
• chore(ci): removed paths-ignore filter; (#6080)
• chore(ci): reworked ignoring files logic; (#6079)
• chore(ci): add paths-ignore config to testing action; (#6078)
• feat(withXSRFToken): added withXSRFToken option as a workaround to achieve the old `withCredentials` behavior; (#6046)
• chore(ci): fixed release notification action; (#6064)
• chore(ci): fixed release notification action; (#6063)
• chore(ci): fix publish action content permission; (#6061)
• chore(release): v1.6.1 (#6060)
• chore(ci): Publish to NPM with provenance (#5835)
• chore(ci): added labeling and notification for published PRs; (#6059)
• fix(formdata): fixed content-type header normalization for non-standard browser environments; (#6056)
• fix(platform): fixed emulated browser detection in node.js environment; (#6055)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)