This repository has been archived by the owner on May 3, 2024. It is now read-only.
chore(deps): bump tough-cookie and @americanexpress/fetch-enhancers #1281
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.
Bumps tough-cookie to 4.1.3 and updates ancestor dependency @americanexpress/fetch-enhancers. These dependencies need to be updated together.
Updates
tough-cookie
from 4.0.0 to 4.1.3Release notes
Sourced from tough-cookie's releases.
... (truncated)
Commits
4ff4d29
4.1.3 release preparation, update the package and lib/version to 4.1.3. (#284)12d4747
Prevent prototype pollution in cookie memstore (#283)f06b72d
Fix documentation for store.findCookies, missing allowSpecialUseDomain proper...b1a8898
fix: allow set cookies with localhost (#253)ec70796
4.1.1 Patch -- allow special use domains by default (#250)d4ac580
fix: allow special use domains by default (#249)79c2f7d
4.1.0 release to NPM (#245)4fafc17
Prepare tough-cookie 4.1 for publishing (updated GitHub actions, move Dockerf...aa4396d
fix: distinguish between no samesite and samesite=none (#240)b8d7511
Modernize README (#234)Updates
@americanexpress/fetch-enhancers
from 1.1.4 to 1.1.5Release notes
Sourced from
@americanexpress/fetch-enhancers
's releases.Changelog
Sourced from
@americanexpress/fetch-enhancers
's changelog.Commits
1e778e6
chore(release): 1.1.5 [skip ci]2b484e5
fix(createBrowserLikeFetch): configure tough-cookie for localhost (#57)30e5b74
chore(deps): update semantic release eslint and jest (#56)9e3d305
chore(deps-dev): bump@babel/traverse
from 7.18.0 to 7.23.2 (#55)30a1e81
chore(deps-dev): bump word-wrap from 1.2.3 to 1.2.4 (#54)ac14f44
chore(deps): bump tough-cookie from 4.0.0 to 4.1.3 (#53)1f11ddd
chore(node): add node 18 to releaseb1d5eed
chore(node): add 18 to workflows and remove <16 (#51)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 show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@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)You can disable automated security fix PRs for this repo from the Security Alerts page.