Update dependency connect-mongo to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
connect-mongo	^5.0.0 → ^6.0.0

---

Release Notes

jdesboeufs/connect-mongo (connect-mongo)

v6.0.0

Compare Source

• Breaking: Requires Node.js 20.8+ (aligns with MongoDB driver 5–7 support).
• Compatibility: Supported/tested matrix: Node 20/22/24 + MongoDB driver 5.x–7.x + MongoDB server 4.4–8.0 (peer range remains >=5.0.0).
• Added: Optional timestamps flag to record createdAt/updatedAt on session documents for auditing while keeping the default schema unchanged.
• Added: Pluggable cryptoAdapter interface with helpers createWebCryptoAdapter (AES-GCM via Web Crypto API) and createKrupteinAdapter; legacy crypto options are auto-wrapped and mutually exclusive with cryptoAdapter to avoid ambiguity.
• Fixed: store.clear() now uses deleteMany({}) instead of collection.drop(), preserving TTL indexes and treating NamespaceNotFound as success so clears are idempotent.
• Fixed: Decryption failures in get() now short-circuit after the first callback, preventing double-callback regressions when the crypto secret is wrong.
• Packaging: npm package now ships dual ESM/CJS bundles via tsdown, with an explicit exports map and cleaned type declarations (.d.mts/.d.cts).
• Types: MongoStore and option hooks are strongly typed to avoid any leaks.

---

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: krew.io-source/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: closure-webpack-plugin@2.6.1
npm ERR! Found: webpack@5.94.0
npm ERR! node_modules/webpack
npm ERR!   webpack@"^5.94.0" from the root project
npm ERR!   peer webpack@"^5.0.0" from grunt-webpack@7.0.0
npm ERR!   node_modules/grunt-webpack
npm ERR!     grunt-webpack@"^7.0.0" from the root project
npm ERR!   1 more (terser-webpack-plugin)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"4.x" from closure-webpack-plugin@2.6.1
npm ERR! node_modules/closure-webpack-plugin
npm ERR!   closure-webpack-plugin@"^2.5.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: webpack@4.47.0
npm ERR! node_modules/webpack
npm ERR!   peer webpack@"4.x" from closure-webpack-plugin@2.6.1
npm ERR!   node_modules/closure-webpack-plugin
npm ERR!     closure-webpack-plugin@"^2.5.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-01-08T19_29_35_671Z-debug-0.log