Bump cookie and @clerk/nextjs

[dependabot]

Bumps cookie to 0.7.0 and updates ancestor dependency @clerk/nextjs. These dependencies need to be updated together.

Updates cookie from 0.5.0 to 0.7.0

Release notes

Sourced from cookie's releases.

0.7.0

• perf: parse cookies ~10% faster (#144 by @​kurtextrem and #170)
• fix: narrow the validation of cookies to match RFC6265 (#167 by @​bewinsnw)
• fix: add main to package.json for rspack (#166 by @​proudparrot2)

jshttp/cookie@v0.6.0...v0.7.0

0.6.0

• Add partitioned option

Commits

• ab057d6 0.7.0
• 5f02ca8 Migrate history to GitHub releases
• a5d591c Migrate history to GitHub releases
• 51968f9 Skip isNaN
• 9e7ca51 perf(parse): cache length, return early (#144)
• d6f39b0 Fix tests for old node
• 6bb701f Remove failing scorecard
• ca70da4 test(serialize): additional tests for name, domain and path RFC validations (...
• 47917c9 Iterate whitespace for perf (#170)
• 927d48a Add main to package.json (#166)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by blakeembrey, a new releaser for cookie since your current version.

Updates @clerk/nextjs from 5.6.3 to 5.7.5

Changelog

Sourced from @​clerk/nextjs's changelog.

5.7.5

Patch Changes

• Updated dependencies [e1a26547a]:
  • @​clerk/backend@​1.14.1

5.7.4

Patch Changes

• Updated dependencies [ce40ff6f0, e81d45b72, 752ce9bfa, 99cdf9b67, ce40ff6f0, fb7ba1f34, 2102052c0]:
  • @​clerk/clerk-react@​5.12.0
  • @​clerk/types@​4.26.0
  • @​clerk/shared@​2.9.2
  • @​clerk/backend@​1.14.0

5.7.3

Patch Changes

• Updated dependencies [d64e54c40, 2ba2fd148]:
  • @​clerk/shared@​2.9.1
  • @​clerk/types@​4.25.1
  • @​clerk/backend@​1.13.10
  • @​clerk/clerk-react@​5.11.1

5.7.2

Patch Changes

• Introduces organizationSyncOptions option to clerkMiddleware, which syncs an active organization or personal account from a URL to the Clerk session. (#3977) by @​izaaklauer

• Updated dependencies [358be296a]:

  • @​clerk/backend@​1.13.9

5.7.1

Patch Changes

• Updated dependencies [fb932e5cf]:
  • @​clerk/shared@​2.9.0
  • @​clerk/clerk-react@​5.11.0
  • @​clerk/types@​4.25.0
  • @​clerk/backend@​1.13.8

5.7.0

Minor Changes

... (truncated)

Commits

• bf83dd5 ci(repo): Version packages (#4353)
• 1647b9e ci(repo): Version packages (#4336)
• 0d923c1 ci(repo): Version packages (#4323)
• d724a36 ci(repo): Version packages (#4307)
• 0d56455 fix(nextjs): do not build test file declarations (#4286)
• 3b6d510 chore(repo): Node 20 / attw change (#4283)
• 0cf6d04 ci(repo): Version packages (#4272)
• 2e369ee ci(repo): Version packages (#4247)
• f6fb8b5 chore(nextjs,clerk-react,clerk-js): Drop the mounted variant of `UserVerifica...
• 3a24de7 fix(repo): Update dependency next [SECURITY] (#4186)
• Additional commits viewable in compare view

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.

[codara-ai-code-review]

Potential issues, bugs, and flaws that can introduce unwanted behavior:

1. package-lock.json: The changes in version numbers indicate an update in dependencies, which may introduce breaking changes that are not accounted for. It's advisable to review the release notes of those updated packages to ensure that there are no breaking changes that could affect the current implementation.

2. package-lock.json: Several dependencies have been added and updated (e.g., nanoid, recma-*). Ensure that any new features or changes don't conflict with existing code and that all usages of these libraries are compliant with their current versions.

3. package.json: The update of @clerk/nextjs from ^5.3.4 to ^5.7.5 without a corresponding change in the lock file suggests potential inconsistency. Make sure the package-lock file is properly updated to reflect all modifications and synced with package.json.

Code suggestions and improvements for better exception handling, logic, standardization, and consistency:

1. package-lock.json: After major modification on dependencies it is good practice to run npm audit to check for vulnerabilities introduced with updated packages, and act accordingly by either fixing or remediating them.

2. package-lock.json: If certain packages are being updated, ensure that the application is tested to verify that these updates do not introduce regression. Consider writing integration tests if not already in place to cover critical paths.

3. package.json: It's recommended to use a specific versioning strategy and to include a commit or prerelease related section in the project release notes, documenting the dependency changes explicitly to facilitate tracking and troubleshooting in the future.