tough-cookie
6.1.0 · 6 Nov 2026BSD-3-Clause202.3M / weekRepositorynpmAtom feed
Upgrading tough-cookie From 6.0.0 to 6.1.0
3 releases in betweenevery note read
Reading releases, release notes and advisories…
Release by release
- New
New exported
PrefixSecurityModetype for theprefixSecurityoption (#659, #667).
- New
- Fixed
Avoid decoding URL authority part
- Fixed
6.0.1nothing new or fixed in the note
10 other lines we could not sort, mostly version bumps
- 6.1.0
__Host-cookies now need an explicitPath=/attribute. Having the default path come out as/is no longer enough (#608). - 6.1.0
Cookie.validate()now returnsfalsefor names that aren't valid HTTP tokens, such as empty names, names with separators or control characters, and non-ASCII names. Parsing and storage are unchanged (#650). - 6.1.0
An explicit
SameSite=Noneis now kept when serializing withCookie.toString()andgetSetCookieStrings(); it used to be dropped (#639). - 6.1.0
An IPv4 address in the
Domainattribute is now accepted instead of being treated as a public suffix (#630). - 6.1.0
The
getCookiesSync,getCookieString*,getSetCookieStrings*andsetCookieSyncmethods now accept aURLas well as astring, matching their async counterparts (#655). - 6.0.2
Review Section 5.1.3. Domain Matching
- 6.0.2
Dependency bumps in too many PRs to bother enumerating
- 6.0.1
Review Section 5.1.1. Dates
- 6.0.1
Adopt npm trusted publishing (OIDC)
- 6.0.1
Bump tldts from 7.0.23 to 7.0.25 in the production-dependencies group
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.