deps: bump cookie from 1.1.1 to 2.0.1 - #297
Merged
Merged
Conversation
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
dependabot
Bot
added
the
dependencies
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/cookie-2.0.1
branch
from
August 10, 2026 08:06
d0ee03d to
669012c
Compare
Bumps [cookie](https://github.com/jshttp/cookie) from 1.1.1 to 2.0.1. - [Release notes](https://github.com/jshttp/cookie/releases) - [Commits](jshttp/cookie@v1.1.1...v2.0.1) --- updated-dependencies: - dependency-name: cookie dependency-version: 2.0.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/cookie-2.0.1
branch
from
August 10, 2026 10:02
669012c to
9c6fcb0
Compare
cookie 2.0 renamed its exports: serialize → stringifySetCookie (taking one
{name, value, ...options} object) and parse → parseCookie. Output verified
byte-identical for our call shape, including that httpOnly:false still OMITS
the flag — the CSRF cookie must stay JS-readable for the Double Submit
pattern.
cookie v2 is also pure ESM, which jest could not parse. The allowlist entry
in customJestConfig alone is dead config: next/jest PREPENDS its own
transformIgnorePatterns and patterns are OR'd, so the package must be
injected into the generated pattern after createJestConfig resolves. With
that, the 21 csrf tests actually run again (they were failing to even load).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Collaborator
|
Pushed the cookie v2 API migration: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 cookie from 1.1.1 to 2.0.1.
Release notes
Sourced from cookie's releases.
Commits
51c48542.0.184068f8Increment=index when parsingset-cookie(#280)e5164de2.0.0ddd3ad4Remove deprecations from README (#279)581e9dfApplyencodeto empty cookie values (#277)6a4ec43Upgrade deps (#278)f6d0482Switch to ESM (#273)b05ae23Add release workflow (#264)15d7996Remove deprecated code paths (#272)4f7c94aOptimizeencodeperformance (#269)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for cookie since your current version.