Changes

What shipped in which version — assembled from the tags, not written by hand.

Versions and the pin

Every release has a tag, and a tag is how the kit is pinned. The version number moves only at a release, so a commit between two releases carries the previous one's number — which is why a pin names a tag and never a commit.

"@forgmatic/ingot": "github:zm-sw/ingot-ui-kit#v1.1.1"

The list is assembled at build time from the tags. A hand-kept list of releases is a list that is one release behind.

Releases

v1.1.12026-09-04
  • Automatický release z registru doc stránek (v1.1.0 -> v1.1.1).
  • Změněné komponenty: IngotStepCard, IngotTopNav.
v1.1.02026-09-03
  • Automatický release z registru doc stránek (v1.0.4 -> v1.1.0).
  • Nová primitiva: IngotDisclosure.
  • Změněné komponenty: IngotIcon, IngotSearchInput.
v1.0.42026-09-03
  • Automatický release z registru doc stránek (v1.0.3 -> v1.0.4).
v1.0.32026-09-03
  • Automatický release z registru doc stránek (v1.0.2 -> v1.0.3).
v1.0.22026-09-03
  • Automatický release z registru doc stránek (v1.0.1 -> v1.0.2).
  • Změněné komponenty: IngotIcon.
v1.0.12026-09-03
  • Automatický release z registru doc stránek (v1.0.0 -> v1.0.1).
  • Změněné komponenty: IngotIcon, IngotMegaMenu, IngotTopNav.
v1.0.02026-09-02

This tag has no notes attached.

The “since” badge

Every component page carries a “since” badge. Nobody writes it: at build time each tag is asked which pages it contained, and the first tag that carries a page is the version the primitive shipped in.

The badge therefore answers the question the reader actually arrives with — does this exist in the version I pinned — instead of sending them to the repository to find out.