Skip to content

v0.26.6

Choose a tag to compare

View all tags
@Innei Innei released this 13 Jun 17:26
· 6 commits to main since this release
v0.26.6
a3a81ba
This commit was signed with the committer’s verified signature.
Innei Innei
GPG key ID: 0F62D33977F021F7
Verified
Learn about vigilant mode.

Summary

Patch release driven by a peer-dependency hygiene fix: @haklex/rich-renderer-image previously declared jotai as a runtime dependency pinned to an exact version (2.19.1), which guaranteed downstream consumers (Yohaku, Shiroi, mx-core/admin) installed a duplicate jotai instance. Jotai stores atoms in a React Context — a duplicate instance silently disconnects the renderer's image-edit state from the host app. This release relocates jotai to peerDependencies (>=2) so consumers' own jotai becomes the single instance, matching the pattern used for lexical, lucide-react, and react. The workspace closure expansion republishes rich-editor, rich-editor-ui, rich-style-token, and rich-headless to keep cross-deps resolvable.

Breaking Changes

None for known downstream apps — Yohaku, Shiroi, and mx-core/admin already declare jotai. Consumers of @haklex/rich-renderer-image that did NOT previously declare jotai must now add it to their dependencies (any >=2 version). pnpm/npm will surface this as an unmet peer warning on install.

Bug Fixes

  • @haklex/rich-renderer-image: move jotai from dependencies (exact 2.19.1) to peerDependencies (>=2) to prevent duplicate-instance bug — the renderer's atom store now shares the host app's jotai instance instead of forking its own.

Other

  • Dependency hygiene: bumped within semver ranges across the workspace (shiki, jotai, prettier, turbo, vitest, knip, stylelint, react-router-dom, @types/node).
  • Tooling: lint-staged 16 → 17 (Node 22+ required; engines.node updated accordingly), code-inspector-plugin 1.5 → 1.6, react-tweet 3.4.2 → 3.4.3.
  • These tooling updates are dev-only and do not affect consumers.

Bump rationale

Package Diff signal Bump
@haklex/rich-renderer-image Moved jotai from dep to peer. No public export, signature, or CSS class change. All identified downstreams already satisfy the new peer. patch

Closure expansion (forward, via peerDependencies: workspace:^) republishes rich-editor, rich-editor-ui, rich-style-token, rich-headless at the same patch version.

Assets 2
Loading