Skip to content

chore(deps): do not offer keyv or mermaid majors yet - #237

Merged
derrickmehaffy merged 3 commits into
mainfrom
chore/dependabot-ignore-keyv-major
Oct 12, 2026
Merged

derrickmehaffy merged 3 commits into
mainfrom
chore/dependabot-ignore-keyv-major

Conversation

@derrickmehaffy

@derrickmehaffy derrickmehaffy commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

What changed and why

Dependabot's production group (#234) bumped keyv 5.6.0 → 6.1.0 on its own. The redis e2e suite failed on Node 22, 24 and 26 because every purge threw:

REST Cache: failed to purge "api::category.category" after "create"
TypeError: Cannot read properties of undefined (reading 'store')

That error comes from RedisCacheProvider.ts:72, which reads cache.stores[0].opts.store. keyv 6 has no opts at all.

Porting the provider isn't the fix yet:

Fixing the accessor wouldn't be enough either:

This does not block the move to node-redis: @keyv/redis 4 and 5 already use @redis/client and still peer on keyv ^5, so #239 (the plugin-redis v3 move) can land on keyv 5. Only @keyv/redis 6 needs keyv 6. This adds keyv to the major-version ignore list next to @keyv/redis, with the reason.

mermaid majors are ignored too:

Once this is merged, #234 and #231 both need @dependabot recreate so it's rebuilt without the keyv bump. Its other updates (Strapi 5.57, react-router-dom, styled-components) passed every other suite.

Checklist

  • Tests added or updated. N/A, Dependabot configuration only.
  • Conventional commit subjects, branched from main.

🤖 Generated with Claude Code

The production group bumped keyv to 6.1.0 on its own. Both providers pass
their Keyv stores to cache-manager, which still depends on keyv ^5.6 in its
latest release, and @keyv/redis 6 - already held back for its own reasons -
is the release that peers on keyv 6. Alone, the bump broke every redis purge
(#234). keyv has to move together with cache-manager and @keyv/redis, as one
deliberate migration.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…cost

mermaid 12 clips the second line of our flowchart labels and is outside
vitepress-plugin-mermaid's declared peer range. No CI job renders the docs,
so #231 was green while visibly breaking them.

The keyv comment said keyv 6 "no longer populates" opts.store; it has no
opts at all. More importantly it implied the port was an accessor fix. It
is not: keyv 6 bridges @keyv/redis 3 and drops the default namespace, which
would turn purges into silent no-ops, and the @keyv/redis that supports it
moves to @redis/client while the redis plugin is being rewritten.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@derrickmehaffy derrickmehaffy changed the title chore(deps): do not offer keyv majors until cache-manager supports them chore(deps): do not offer keyv or mermaid majors yet Oct 12, 2026
@keyv/redis 4 and 5 already run on @redis/client and peer on keyv ^5, so
the provider's move to node-redis (#239) can land without keyv 6. The
previous comment implied the two had to move together.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@derrickmehaffy
derrickmehaffy merged commit 7df7c37 into main Oct 12, 2026
13 checks passed
@derrickmehaffy
derrickmehaffy deleted the chore/dependabot-ignore-keyv-major branch October 12, 2026 23:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant