Fixed #

• bloom_framework could not be resolved by any consumer outside this repository. Its hosted constraints on bloom_seo (^0.1.1) and bloom_js_native (^0.2.0) contradicted what its own siblings require — bloom_server ^0.2.0 depends on bloom_seo ^0.2.0, and both bloom_seo and bloom_server depend on bloom_js_native ^0.3.0 — so pub get failed with "version solving failed" on 0.3.1 and 0.4.0. The constraints are now ^0.2.0 and ^0.3.0, matching the versions the monorepo's dependency_overrides already resolve to, so the published package resolves to exactly what is built and tested here. The overrides had masked the contradiction locally.

Bloom Framework no longer depends on Flutter's Material library. Every widget it ships is now built on package:flutter/widgets.dart and the Bloom UI primitives.

Breaking #

• BloomApp.theme and BloomApp.darkTheme are now BloomTheme rather than ThemeData, and BloomApp.themeMode is BloomThemeMode rather than ThemeMode. Pass BloomTheme.light / BloomTheme.dark (or your own BloomTheme) instead of a ThemeData. There is no Material-free equivalent of ThemeData, so this change is unavoidable rather than stylistic.
• pumpBloomApp's theme: parameter follows the same change, from ThemeData? to BloomTheme?.

Added #

• bloom_ui is now a dependency. The framework's widgets — the app shell, the 404 page, the OTA update banner and dialog, the dev inspector overlay and the native view fallback — are built from Bloom UI primitives rather than Material ones.

Changed #

• BloomApp now wraps BloomApp.router from bloom_ui instead of MaterialApp.router. Note that bloom_ui also exports a BloomApp; framework sources import bloom_ui under a ui prefix, and the framework does not re-export it, so consumers see no ambiguity.
• BloomMobileApp's dark theme is expressed as a BloomTheme, preserving its exact palette (0xFF09090B surface, 0xFF6366F1 primary, 0xFF14141A secondary) and its type scale.
• The dev inspector's tab strip is now token-themed via BloomTabs; its Material labelColor/indicatorColor overrides no longer apply.

Fixed #

• The native text input's focus ring was previously drawn by Material's focusedBorder. It is preserved via the new BloomEditableField.focusedDecoration.
• The OTA update banner's download indicator is determinate again — it fills with real download progress rather than spinning indefinitely.

Fixed #

• Bumped bloom_server dependency constraint from ^0.1.0 to ^0.2.0 — the stale constraint was incompatible with any sibling package (bloom_cache, bloom_i18n) requiring bloom_server ^0.2.0, breaking pub get in any app combining them.

Added #

• Fabric-Grade Native Mobile AST Engine (bloom_mobile.dart):
  • BloomFlexLayout & RenderBloomFlex: Multi-pass Flexbox layout solver resolving flex-wrap, percentage dimensions, margins, and paddings on mobile devices.
  • BloomLeafRenderBox & RenderBloomLeafText: Direct GPU canvas signal painter bypassing widget tree rebuilds on state changes.
  • BloomNativeInputHost: Persistent native text controller bridge preserving keyboard insets and cursor selections.
  • BloomVirtualList: Viewport sliver recycling for ForEachNode.
  • BloomMobileApp & runBloomMobile: Root mobile application wrapper mounting pure-Dart AST descriptor trees.

Added #

• Automatic OpenAPI 3.1 & Swagger / Scalar Documentation: BloomApiRouter now includes enableOpenApi() and toOpenApiSpec() for zero-config, single-line API documentation generation. The router automatically discovers registered routes, parameters, HTTP methods, and tags, rendering interactive Scalar (/api/docs) and Swagger UI (/api/swagger) consoles with official Bloom vector branding and dark mode styling.
• HTTP HEAD Method Support for GET Routes: BloomApiRouter now transparently supports HEAD requests on all GET endpoints, returning accurate headers and status codes without body serialization.

Changed #

• Bloom API Router Specificity & Regex Matching: Fixed root / path matching and wildcard resolution.

Added #

• Prerender readiness signal for headless-browser SSG/SSR: BloomApp now enables Flutter's semantics/accessibility tree and signals window.__BLOOM_PRERENDER_READY__ after its first frame, on web only (no-op elsewhere). This is consumed by bloom_cli's new real headless-Chromium prerendering pipeline (bloom build web --static/--server) to know when a page has actually finished rendering before capturing its DOM.

Fixed #

• BloomRequest.params defaulted to a const {} map: any middleware that tried to attach convenience context (e.g. bloom_i18n's resolved locale, bloom_auth_server's verified auth_user_id/auth_roles) on a request with no path parameters crashed with Unsupported operation: Cannot modify unmodifiable map the moment it ran. params now always defaults to a fresh mutable map.
• BloomApiRouter discarded per-request middleware context on every route match: route dispatch built a new BloomRequest via copyWith(params: ...) after global middlewares had already run and attached state (params, or framework-internal Expando-backed context) to the original request instance — silently dropping it before route-specific middlewares and the handler ever saw it. Path parameters are now merged into the same request instance in place, so global middleware state (locale resolution, auth claims, etc.) survives all the way to the handler.
• A pure-Dart server importing bloom_server.dart transitively pulled in package:flutter: bloom_realtime's single barrel exported both server-side (BloomChannelHub) and Flutter-app-only (RealtimeQueryBridge, which depends on BloomData's signals_flutter-backed reactivity) code together, so any backend depending on it could not run under a plain dart run/dart compile. Split into bloom_realtime.dart (server-safe) and bloom_realtime_client.dart (Flutter client extras). Added a new Flutter-independent bloom_core.dart barrel (env config, DI container, logger) re-exported from bloom_server.dart, and a bloom_data.dart barrel for the client query/cache layer — server code should never import bloom.dart directly.

Fixed #

• BloomEnv crashed on first read of any unset key: get/getOrNull/getInt/getDouble/getBool/contains fell back to bool.hasEnvironment(key) with a runtime key, but that constructor only accepts a compile-time constant — every call threw bool.hasEnvironment can only be used as a const constructor the moment a requested key wasn't already loaded into the runtime map. Since routes commonly read config on their very first build, this could blank the initial frame. The dynamic dart-define fallback is removed; apps that need --dart-define values now seed them explicitly at boot via the new BloomEnv.loadDartDefines(...), using literal keys the same way Bloom.boot() already does for BLOOM_FLAVOR.
• Scaffolded apps and the dev overlay showed a generic purple Material icon (Icons.local_florist_rounded) instead of the Bloom brand mark: added a real BloomLogo widget that renders the actual five-petal gradient flower (matching bloom-logo.tsx) and swapped it in across the CLI scaffold template, the dev inspector overlay, and both example apps.

Breaking #

• Canonical cache-key normalization: BloomData.normalizeKey now canonicalizes recursively — Map segments have their entries sorted, and Iterable segments are canonicalized element-wise. Keys whose map segments differed only by insertion order previously resolved to different cache slots and now correctly resolve to the same one. Any code that persisted or compared the raw output of normalizeKey must be re-keyed.

Fixed #

• Invalidation reached only cached queries: BloomData.invalidateQueries signalled only queries that already held a cache entry, so a query that had never completed a successful fetch (still loading, or in the error state) was never notified. Calling invalidate() on a failed query is now a working retry path. Prefix matching is evaluated on : segment boundaries, so ['users'] matches ['users','detail','42'] but not ['usersettings','1'].
• Garbage collection could deafen live queries: expired entries were evicted and their invalidation stream controllers closed without regard for active subscribers, permanently stopping a mounted query from receiving invalidations. Eviction now requires a zero listener count, and a controller is never closed while a listener is attached. The same guard now covers getEntry(), getQueryData() and removeEntry(), which each closed controllers as a side effect of reading or removing an expired entry.

Added #

• BloomData.releaseListener(key): releases a listener slot acquired via BloomData.onInvalidated(key). BloomQuery.dispose() calls it automatically, so it is only needed when subscribing to onInvalidated directly.

• Core Runtime & Boot Lifecycle: Single-call Bloom.boot() with dependency injection container (inject<T>(), provideSingleton<T>()).
• Signals State Management: High-performance fine-grained reactivity (signal, computed, effect, batch, Watch, SignalBuilder).
• Filesystem Routing: File-based route conventions (index.dart, [id].dart, _layout.dart ShellRoutes, route guards).
• Bloom Data & Offline Engine: Stale-while-revalidate caching (BloomData.query, BloomData.mutation), deduplication, TTL GC, and OfflineMutationQueue.
• Native Architecture & Prebuild: Declarative native plugin integrations (BloomPermissions, BloomSecureStorage, BloomNotifications, BloomCamera, BloomDeepLinks).
• DevTools & Dev Server: UDP broadcast discovery on port 5354, visual DevTools overlay, BloomNetworkInspector with request replay.
• Full-Stack Server & SSR Engine: BloomApiRouter, BloomRequest, BloomResponse, API route handlers, and middleware.
• Observability & Error Telemetry: Automatic crash capture, breadcrumbs timeline, symbol packaging, and fingerprinting.
• Full-Stack Adapters: Official Supabase and Serverpod client & repository adapters.