Skip to content

Changelog

This page tracks the highest-signal changes for evaluators and adopters. It is not meant to replace commit history. It is meant to explain what changed, why it matters, and what to recheck when you upgrade.

0.1.13

Focus: core-runtime stability, browser correctness, safer exports and scaffolding, and enforceable release gates.

Highlights:

  • browser Back/Forward synchronization no longer pushes duplicate history entries
  • frontend VDOM patches are validated and fail closed with full-state reconnect recovery
  • nested Python render contexts restore their previous ContextVar token correctly
  • application title, favicon, theme CSS, and loading bootstrap values are embedded at safe HTML boundaries
  • missing frontend assets return an actionable HTTP 503 instead of a frozen fallback renderer
  • CSV export neutralizes spreadsheet formulas, uses a browser-safe download lifecycle, and emits Excel-friendly UTF-8 output
  • ChatInput respects IME composition and preserves back-to-back change/submit events across one render generation
  • progress fills now map friendly color names to defined theme tokens, so an 85 value visibly fills 85% instead of rendering transparent
  • runtime version reporting now follows the source/package version instead of an unrelated globally installed release
  • incremental patches recursively serialize VNodes nested in changed props
  • brickflowui new rejects traversal, absolute, reserved, and unsafe scaffold targets before writing
  • frontend Vitest and ESLint gates now run in CI alongside Python, docs, and package builds
  • obsolete duplicate examples were removed in favor of the maintained flagship set

Upgrade notes:

  • source checkouts must build the React frontend; missing assets are now an explicit deployment failure
  • rebuild custom containers or Databricks App bundles so they include the 0.1.13 hashed frontend assets
  • run the browser history, CSV export, and chat-input checks in Stability Contract
  • CatalogBrowser, WarehouseSelector, and JobTrigger remain experimental until their dedicated end-to-end Databricks contracts ship

0.1.12

Focus: framework hardening, stronger product surfaces, enterprise-facing docs, and broader example coverage.

Highlights:

  • broader dashboard and workflow surface including pipeline, chat, kanban, status, and media patterns
  • stronger loading, theming, and branded runtime behavior
  • responsive shell improvements and richer example apps
  • auth-aware docs and deployment guidance
  • landing page, docs portal, and reference content expanded to better support evaluation

Upgrade notes:

  • review your theme config if you depend on older dark-mode assumptions
  • prefer the latest examples when adopting loading, media, and preset-driven theming

0.1.11

Focus: responsiveness, polish, and reliability in day-to-day builder flows.

Highlights:

  • smoother typing and local-first input behavior
  • stronger loading-state handling across interactive components
  • improved shell behavior for mobile and denser layouts
  • more polished examples and better scaffolding experience

Upgrade notes:

  • if you built custom workarounds for input lag, revisit them against the current runtime
  • retest mobile layout behavior in your main apps

0.1.10

Focus: stabilization and scalability-oriented runtime improvements.

Highlights:

  • deferred frontend tree updates and smoother rerender handling
  • better guidance around performance and local testing
  • stronger docs on runtime behavior

0.1.9 and Earlier

The project moved through several rapid polish and capability passes in the 0.1.x line. If you are upgrading from an older 0.1.x release, use:

Release Discipline Going Forward

Every user-visible library change should update:

  • package version
  • docs references
  • example requirements
  • scaffolded template requirements
  • release-facing upgrade guidance