Packages

tough-cookie

6.1.0 · 6 Nov 2026BSD-3-Clause202.3M / weekRepositorynpmAtom feed

Upgrading tough-cookie From 5.1.1 to 6.1.0

5 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 5.1.1Newest 5.x5.1.2
1
change to make
0
advisories fixed
3
new
2
fixes

Before you upgrade

Tick each one off as you go
  • Breaking6.0.0

Release by release

  1. 6.1.0

    6 Nov 20261 new
    • New

      New exported PrefixSecurityMode type for the prefixSecurity option (#659, #667).

  2. 6.0.2

    7 Jul 20261 fix
    • Fixed

      Avoid decoding URL authority part

  3. 6.0.1nothing new or fixed in the note

  4. 6.0.0

    Migration needed14 Aug 20252 new
    • Breaking

      Localhost connections over http will now be considered secure by default. For more information, see the README documentation and API Docs for how to configure this feature.

    • New

      Add RFC 6761–compliant localhost loopback checks so secure cookies work on localhost (fixes: #382)

    • New

      Support publishing of both ESM and CJS

  5. 5.1.2

    28 Feb 20251 fix
    • Fixed

      Fix regression bug in domainMatch

27 other lines we could not sort, mostly version bumps
  • __Host- cookies now need an explicit Path=/ attribute. Having the default path come out as / is no longer enough (#608).

    6.1.0
  • Cookie.validate() now returns false for 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=None is now kept when serializing with Cookie.toString() and getSetCookieStrings(); it used to be dropped (#639).

    6.1.0
  • An IPv4 address in the Domain attribute is now accepted instead of being treated as a public suffix (#630).

    6.1.0
  • The getCookiesSync, getCookieString*, getSetCookieStrings* and setCookieSync methods now accept a URL as well as a string, matching their async counterparts (#655).

    6.1.0
  • Review Section 5.1.3. Domain Matching

    6.0.2
  • Dependency bumps in too many PRs to bother enumerating

    6.0.2
  • 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

    6.0.1

5 internal lines (docs, tests, tooling) left out.

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.