Gallery freshness ("update available")
The gallery is a set of well-known design systems you can browse and pull into your workspace. Each one was captured at a point in time, and its upstream project keeps shipping. Gallery freshness tells you when a system in the gallery has fallen behind its upstream release, so a version you install isn't quietly stale.
What you'll see
On a gallery card and on the system's detail page, a system may show:
- A version - for example
v0.1.6. This is the upstream version the gallery copy was captured at. - An amber dot + "update available" - the upstream project has shipped a newer version than the one in the gallery. On the detail page this links out to the upstream release so you can see what changed.
A weekly check polls each tracked system's upstream (its npm package or GitHub releases) and records the latest version. The badge reflects the most recent successful check: if a check can't reach a registry, the last known result is kept rather than cleared, so a temporary outage never makes a real "update available" disappear.
Why only some systems show it
"Update available" appears only when we can make an honest comparison: the gallery copy has a real pinned version and the upstream has a newer one. Some gallery systems were captured from a moving branch rather than a tagged release, so there's no exact version to compare against - those show no freshness badge rather than a guessed one. As those systems are re-captured from pinned releases, their freshness turns on at the next weekly check.
A couple of systems (for example copy-paste component collections and large multi-package projects) don't have a single "the version" at all. For those, the card links you to the upstream site to check for yourself instead of showing a number.
FAQ
Does "update available" change my installed copy? No. It's a heads-up, not an action. Your installed design system stays exactly as it is until you choose to re-import. The badge only tells you the upstream moved.
How current is the badge? The check runs weekly, so a brand-new upstream release can take a few days to appear. The version shown is always a real upstream version, never a guess.
A system I care about shows no version at all - why? It was captured from a source without a clean, comparable version (a moving branch, a copy-paste collection, or a multi-package project). Use the "Visit site" link on the detail page to check upstream directly.