Ark UI changelog blocks.

200 sections that show what shipped: release timelines, version tabs, filters, code diffs, migration guides, API and SDK changes, rollouts, incidents and release metrics. The gallery sorts them into 14 groups: Lists and timelines, Spotlights and media, Filters and browsing, Votes and sharing, APIs and integrations, Code and commits, Deploys and rollouts, Data and config, Packages and versions, Security and audits, Incidents and uptime, Metrics and charts, Roadmap and customers, Contributors.

For a timeline of releases use Release Timeline Changelog or Compact Timeline Changelog. For one version at a time use Version Tabs Changelog, and to filter by type Filterable Changelog. For upgrades use Breaking Changes Changelog and Migration Guide Changelog, for following along Subscribe Updates Changelog and RSS Feed Changelog, and for versioning rules Semantic Versioning Changelog.

No. Each block has its releases typed into the file as plain objects with a version, an ISO date, a type and a sentence. Nothing reads git, GitHub, npm or a markdown file, so you generate the data from your own release source and pass it in.

A changelog block lists changes by version, with a type tag such as New, Improved, Fixed, Deprecated or Security, a date and a short line. The blog blocks lay out articles. Use a changelog block for release notes and a blog block for the story behind a release.

Replace the RELEASES (or VERSIONS) array at the top of the file with objects matching its interface: for example in Version Tabs Changelog each version has a name, an ISO date and a list of changes, and each change has a kind and a text. Dates are fixed ISO strings, never computed from today, so store the shipping day.

The types are small objects with an id, a label and an icon, declared once (NEW, IMPROVED, FIXED, SECURITY) and shared by the changes. In Filterable Changelog the KINDS array drives the filter choices and their counts, which are counted from the releases, so adding a kind to that array and tagging releases with it adds its choice.

Subscribe Updates Changelog checks the address, keeps focus in the field when it is empty or malformed, and then states what would happen. Its comment marks the spot: send the email and the chosen frequency (every release or a weekly digest) to your mailing-list provider there. The block sends nothing itself.

RSS Feed Changelog offers RSS 2.0, Atom and JSON Feed, swaps the feed address when the format changes, and its Copy button really puts the address on the clipboard. The addresses are typed, so replace them with the URLs your site generates, and render the latest entries from the same data your feed uses.

Breaking Changes Changelog is a table where each row holds the old call in a del element marked "-", the new call in an ins element marked "+", who it affects and a migrate-by day, with a codemod command and Copy button under it. Code Diff Changelog plays a diff of one function with removed lines struck through. Put your own old and new calls and your codemod command in the typed data at the top of each file, such as DIFF_LINES for the diff.

Feedback Votes Changelog keeps the Yes and No counts and the "What was missing?" note in the page, so a reload resets them. Send each vote and note to your API from the toggle and Send handlers, and load the counts back as the initial values. The share that said yes is worked out from those counts.

This page lists 200 of the category's 200 changelog blocks for React on Ark UI. The category comes in React (Base UI, React Aria, Ark UI and Radix UI), Vue, Svelte and Solid; the framework and UI library pickers at the top of any block's page switch between them.

The changelog blocks here are written on Ark UI primitives; the layout, the copy and the theme tokens are the same on every base, and the install path follows it (/r/ark/changelog-ab-test-results.json). The other bases are one picker away from /changelog-block/ark.

Each block is TypeScript and Tailwind CSS v4, styled with your theme's tokens, and imports our components (installed with it) on Ark UI. Icons come from lucide-react.

Open a block, copy its command and run it: `npx shadcn@latest add` with the block's registry URL, such as /r/ark/changelog-ab-test-results.json for A/B Test Results Changelog. The code is copied into your project and it's yours to edit.

The block's file and the components it imports: A/B Test Results Changelog brings Badge and Guides, installed before it. Nothing else changes in your project.

Use the filters above the grid: 14 kinds of changelog block, led by deploys and rollouts (20), lists and timelines (19), spotlights and media (19) and filters and browsing (17), and sort by popular or name. A good first look: A/B Test Results Changelog, Access Control Changes Changelog and Accessibility Log Changelog. Each card opens the block's live page.

Every block draws the same page column and side rails with a top rule only (the Guides component), so a changelog block lines up with the one above and below it. Stack one per section and the rails read as a single drawing; pick across the release notes, engineering and operations kinds.

Open its page and use the full-screen viewer (/view/changelog/ark/ab-test-results) or the device-width previews. Every preview is free for everyone; only the code needs Pro.

Each changelog block uses semantic HTML: one heading level, real lists and labelled controls. Interactive parts sit on Ark UI, a headless library that follows the WAI-ARIA patterns, and the layouts use logical properties so they hold in right-to-left languages.

Yes. They use semantic tokens only (bg-card, text-muted-foreground), never palette colors, so they follow your preset, radius and dark mode. The primary color marks one action per block and is never a background.

No animation library: the changelog blocks' motion is CSS (transitions, entrance animations and SVG), and it stands still under prefers-reduced-motion.

The previews are free for everyone. The code of all 200 changelog blocks is Pro, as is every block: Pro unlocks the code, the install command and the MCP.

Only with a Team or Organization license: client work, SaaS products and anything your users pay for. The Individual license is for personal, non-commercial projects. See the license page for the full terms.

You keep using what you installed in your existing projects, but get no new downloads or updates, and the MCP stops answering. A Lifetime license includes all future updates.

No. You can use them in your own End Products, but not redistribute the code or designs on their own, or in a UI library, kit, template or website builder.

With Pro, yes: the MCP server (22 tools, one personal URL from /dashboard/mcp) lets your agent search_blocks for a changelog block, read it with get_block and install it on your React on Ark UI stack.

Pass `category: "changelog"` to search_blocks to search only the 200 changelog blocks, or to list_blocks for the 14 groups with their blocks. get_block then returns one with its install command.

plan_page plans a page as a stack of blocks for a brief. Pass `sections` with category ids, such as ["hero", "changelog", "footer"], to force the order; each section gets a pick and two alternatives, and get_block installs the stack.