Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Dashboard blocks

Pro

Release Tracker Dashboard Block for Solid

Tick the unreleased changes to include and see the next version number, why it goes up and a changelog preview, then cut it into the releases list as the newest Beta.

Framework
UI library

Preview

Preview width

Installation

Part of Pro
Pro unlocks the code and one-line install of every Pro button and text effect, plus the MCP for your AI editor.
Get ProSign in
Have Pro already? Sign in to open it.Opens here as soon as you're Pro.

Overview

Work out what the next version should be with this release panel for Solid with Ark UI. A hairline frame with a plus mark on each corner opens with Tabs. Unreleased lists eight Shipgate changes, each with a type badge for Breaking, Feature or Fix, its pull request and a Checkbox to include it; Releases lists the five past versions with a status word and their feature and fix counts. Under the changes a card names the next version from what is ticked, says why ("A feature is included, so the minor number goes up") and previews the changelog of those changes, and the foot's Shine Button cuts it. It's built from Tabs, Checkbox, Badge, Empty and Guides. For release planning and changelog tools.

FAQ

How is the next version chosen?

Any ticked Breaking change raises the major number and resets the others. Otherwise any ticked Feature raises the minor number. Otherwise a ticked Fix raises the patch number. With nothing ticked there is no release and the button says so.

What does Cut do?

It moves the ticked changes out of Unreleased and adds the new version to the top of Releases as Beta, counting its features, fixes and breaking changes. The previous Latest becomes Stable, and the view switches to Releases. No tag, build or publish happens.

How do I fill it with my changes?

Edit CHANGES (an id, a type, a pull request number and a title) and PAST (a version, a status, a date and the counts). The first entry of PAST is the current version the bump starts from.

What if I cut every change?

Tick the two breaking changes and cut: Unreleased then shows an empty state, in the same height as the list, and the next version reads "No release".

What stays local, and how do I wire it for real?

Everything is held in the page and resets on reload. To wire it up, load the merged changes since the last tag, and call your release pipeline from cut with the version it shows.

How does it look on a phone?

The next version card sits under the list, the changelog preview wraps, and the foot is pinned to the bottom of the screen.

All 200 dashboard blocks