NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
Transform markdown directories into documentation websites with generated navigation, search, theming, and rich markdown components. Built on Jaspr.
Last release 15 days ago
23 Sep 2026
Ships on a steady schedule
a new release about every 2 weeks
Nearly every release is documented
notes for 3 of 3 stable releases
Nothing withdrawn
no release was ever pulled
1 months old
3 releases · first in 2026
One column per month.
Markdown text extraction reads Arcane Jaspr's Flutter-style Text.data property.
Text.data property.widget, and navigation layouts use numeric
spacing while retaining their stretched columns.--dart-define option.Design-contract tests prevent decorative gradients, colored glows, pill labels, rounded one-sided borders, remote font loading, and retired nested sur
markdown-alert classes (jaspr_content's built-in GitHub-style callouts)kb-callout styles for CalloutExtensionSearchIndexGenerator - Generates a search-index.json file from the navigation manifestweb/search-index.json during build (enabled by default)generateSearchIndex: false in KnowledgeBaseApp.create()icon attribute.jaspr_content typography tokens to the bundled Arcane
font families instead of inheriting its Open Sans and JetBrains Mono stacks.KBIcon.KBTagChip API, and the
PathChip rich-markdown alias./assets/fonts/lucide/lucide.woff2 URL supplied
by the active stylesheet and does not repair unsupported sources.sparkles icon name and its documentation.NavSection.fromYaml and the retired Fields, TreeItem, and
ColorItem rich-markdown aliases without compatibility shims.KBStyles.Example docs site failed to compile (and broke the GitHub Pages deploy): main.server.dart still constructed ShadcnKnowledgeBaseRenderers, NeonKnowledg
main.server.dart still constructed ShadcnKnowledgeBaseRenderers,
NeonKnowledgeBaseRenderers, and NeubrutalismKnowledgeBaseRenderers,
which moved to the arcane_jaspr_kb package. The example now depends on
and imports arcane_jaspr_kb.stylesheet: to KnowledgeBaseApp.create, with no stylesheetOptions) rendered a completely blank page. The style-slot system synthesizes one slot with id default, but the active-slot id resolved to '' on both the server (KBLayout) and the client runtime (_fallbackStylesheetId), so no slot ever matched and every slot stayed display:none/hidden. A single synthesized slot is now always active server-side, and the client fallback id is default, so single-theme docs render correctly. Multi-stylesheet sites are unaffected.DefaultKnowledgeBaseRenderers.showTopBarBranding returned a hardcoded false, so KBs using the default renderers (e.g. single-stylesheet apps) left the top bar's left side empty (only a desktop-hidden hamburger) and pushed the brand into the sidebar. It now returns data.showNavigationBar && data.useTopPosition (matching the shadcn/neon/neubrutalism renderers), so the brand renders top-left in the standard position when the nav bar is top-positioned.autoHide on the documentation top bar (KBTopBar and KnowledgeBaseRenderers.topBar), default false. When enabled, the top bar hides on scroll-down and reappears on scroll-up (via a data-kb-autohide marker, scoped CSS, and a throttled scroll-direction handler). The default (always-visible sticky bar) is unchanged.classes compatibility. Updated for arcane_jaspr's wrapper widgets (ArcaneDiv/ArcaneSpan/ArcaneParagraph/ArcaneHeading/ArcaneLink/…) now taking classes: List<String>? instead of String?. Every internal classes: argument across the layout (kb_page_nav, kb_changelog, kb_related_pages, kb_rating, kb_layout) and rich-markdown components now passes a single-element list, so the rendered class="..." output is byte-identical. Requires the corresponding arcane_jaspr release; bump the arcane_jaspr constraint once it is published.NeonKnowledgeBaseRenderers simplified to use the standard DefaultKnowledgeBaseRenderers docs chrome (top bar / sidebar / content), matching ShadcnKnowledgeBaseRenderers. Removed the bespoke shell/neonMobileDock/rail/stage/command-drawer overrides (the neon-kb-nav-rail, neon-kb-stage, neon-kb-mobile-dock, etc. layout) whose styling had been retired, so the Neon docs no longer render an unstyled, collapsed chrome. The Neon theme now styles the standard kb-* chrome.KnowledgeBaseRenderers (ShadcnKnowledgeBaseRenderers, NeonKnowledgeBaseRenderers, NeubrutalismKnowledgeBaseRenderers, Win95KnowledgeBaseRenderers) moved out of lexicon into their respective arcane_jaspr theme packages, which now depend on arcane_lexicon and extend the exported DefaultKnowledgeBaseRenderers. Consumers pass them explicitly via KBStylesheetOption.knowledgeBaseRenderers. The internal _defaultRenderersFor id-switch (which auto-resolved shadcn/neon/neubrutalism) is gone; a stylesheet option without an explicit renderer now falls back to DefaultKnowledgeBaseRenderers.Your coding agent can read these notes before it upgrades. Set up the MCP server →