v0.6.7

Release Date: August 17, 2026

---

🐛 Bug Fixes & Stability

• Draft Creation & Cache Synchronization — Fixed an issue where creating an entry directly from the Drafts menu failed to register the draft state properly. Synchronized React Query cache states between the content list view and the global drafts hub to ensure immediate UI updates on draft creation and save operations. ([#286](https://www.google.com/search?q=https://github.com/fdemusso/BeechCMS/issues/286), [#289](https://www.google.com/search?q=https://github.com/fdemusso/BeechCMS/pull/289))

• Live & Pending Draft Lifecycle Resolution — Resolved an edge case where published entries with pending draft changes were omitted from global draft counts and excluded from the approval/publishing workflow. ([#289](https://www.google.com/search?q=https://github.com/fdemusso/BeechCMS/pull/289))

• Draft Handler Exception & Shared Email Entrypoint — Resolved missing EntryNotFoundError imports within the API draft controller and unified shared email dispatch entrypoints across API modules. ([#289](https://www.google.com/search?q=https://github.com/fdemusso/BeechCMS/pull/289))

• Forgot Password Localization — Added missing localized labels for the email input field on the password recovery screen alongside dedicated unit test coverage (forgot-password.test.tsx). ([#289](https://www.google.com/search?q=https://github.com/fdemusso/BeechCMS/pull/289))

• Demo Seed Translations — Aligned and corrected semantic translations across Italian and English demo seed datasets. ([#289](https://www.google.com/search?q=https://github.com/fdemusso/BeechCMS/pull/289))

---

🎨 Documentation & UI Overhaul (Docs 2.0)

• Docs Landing Page & Botanical Palette — Redesigned the documentation homepage using the BeechCMS botanical palette, Geist typography, shadcn-inspired neutral tokens, and Lucide vector icons. ([#289](https://www.google.com/search?q=https://github.com/fdemusso/BeechCMS/pull/289))

• Hero Layout & Responsive Transitions — Streamlined the docs hero with a centered layout, smooth Dark/Light mode transitions, and improved mobile navigation. ([#289](https://www.google.com/search?q=https://github.com/fdemusso/BeechCMS/pull/289))

• Architectural Vector SVG Pipelines — Added full vector SVG diagrams across the guides covering API Architecture, Cloudflare Edge Deployment, Botanical Engine Execution, Dual-Table Drafts, Email Delivery, Observability, and Vertical Slice Architecture (VSA) boundaries. ([#289](https://www.google.com/search?q=https://github.com/fdemusso/BeechCMS/pull/289))

• New Dedicated Guides — Added first-project.md for onboarding from scratch, content-editor-guide.md for content creators, and restructured content-api.md for REST API client integrations. ([#289](https://www.google.com/search?q=https://github.com/fdemusso/BeechCMS/pull/289))

• Static Assets Consolidation — Consolidated documentation static assets into docs/public/images to ensure full compatibility with GitHub Pages and VitePress static site builds. ([#289](https://www.google.com/search?q=https://github.com/fdemusso/BeechCMS/pull/289))

---

🧹 Housekeeping & Developer Experience

• Brace Expansion Dependency Conflict Resolution — Removed conflicting brace-expansion overrides that broke minimatch compatibility and caused bundling failures. ([#291](https://www.google.com/search?q=https://github.com/fdemusso/BeechCMS/pull/291))

• TypeDoc Pinning & Symbol Warnings Fix — Pinned TypeScript to 5.9.3 for documentation generation, integrated typedoc-plugin-markdown, resolved symbol link warnings across @beechcms/core and @beechcms/widget-sdk, and explicitly exported Listable and Single types from @beechcms/client. ([#289](https://www.google.com/search?q=https://github.com/fdemusso/BeechCMS/pull/289))

• CI Pipeline Optimization — Temporarily disabled the SonarCloud analysis workflow to eliminate pipeline bottlenecks and speed up build validation. ([#289](https://www.google.com/search?q=https://github.com/fdemusso/BeechCMS/pull/289))

---

🚀 Upgrading

This release contains no breaking changes to existing database schemas or client API contracts. The upgrade is safe for all deployments.