fix(deps): update dependency cookies-next to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
cookies-next	^4.2.1 → ^6.0.0

---

Release Notes

andreizanik/cookies-next (cookies-next)

v6.1.1

Compare Source

What's Changed

• fix: update reactive cookie functions to accept options parameter by @​mowhcen in #​109

New Contributors

• @​mowhcen made their first contribution in #​109

Full Changelog: andreizanik/cookies-next@v6.1.0...v6.1.1

v6.1.0

Compare Source

What's Changed

• feat: Revalidate cookies state by @​greg2012201 in #​102

Full Changelog: andreizanik/cookies-next@v6.0.0...v6.1.0

v6.0.0

Compare Source

What's Changed

• feat: Make hooks trigger rerender. by @​greg2012201 in #​99

Full Changelog: andreizanik/cookies-next@v5.1.0...v6.0.0

v5.1.0

Compare Source

What's Changed

• feat: Hooks by @​greg2012201 in #​92

Full Changelog: andreizanik/cookies-next@v5.0.2...v5.1.0

v5.0.2

Compare Source

Full Changelog: andreizanik/cookies-next@v5.0.0...v5.0.2

v5.0.1

Compare Source

v5.0.0

Compare Source

What's Changed

• feat: add Next.js 15+ support (continuation) by @​greg2012201 in #​87
• feat: add Next.js 15+ support by @​joaopcm in #​86

New Contributors

• @​joaopcm made their first contribution in #​86

Full Changelog: andreizanik/cookies-next@v4.3.0...v5.0.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: frontend/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: frontend@0.1.0
npm error Found: next@14.2.35
npm error node_modules/next
npm error   next@"^14.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer next@">=15.0.0" from cookies-next@6.1.1
npm error node_modules/cookies-next
npm error   cookies-next@"^6.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-02-17T15_37_19_506Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-02-17T15_37_19_506Z-debug-0.log