Skip to content

Changelog

All notable changes to livery-toolroom-store are documented here. The format follows Keep a Changelog, the project adheres to Semantic Versioning, and while it is pre-1.0 a minor version may include breaking changes.

[Unreleased]

Changed

  • The plan records the rulings of 2026-10-18

[0.5.0] - 2026-10-17

Added

  • [coverage] replaces [qa]: the coverage extension declares a package's floor, epsilon and required, a package with tests and no floor is judged at 100, and new projects list coverage by @willemkokke
  • Every package lists its extensions, a contract's kind refuses naming the list to write, and the kind fallbacks, the backend protocol and the kind guards go by @willemkokke

Changed

  • This repository's packages list their extensions by @willemkokke
  • Each tool is required by the extension that runs it, and uv by the base by @willemkokke
  • Remove what the redesigns left behind: the register-and-withdraw functions, dead definitions, leftover sweeps, empty stylesheets and the text naming kinds and seeds by @willemkokke

[0.4.0] - 2026-10-12

Added

  • The tool store's view walk leaves the sync: Store.probe keeps the ref and record checks, audit and audit_views name a damaged view, mend_view views its tree again, and the store's doctor reports and mends under fm doctor --fix by @willemkokke

Fixed

  • A catalogue read roots each tool's index tree under tools/index/, so the store's sweep keeps the records, versions and surfaces a job's entry re-fetched; the sweep keeps the store whole on Gitea's runner, which saves no archive by @willemkokke

[0.3.0] - 2026-10-08

Changed

  • The tool extensions sit inside the workshop's entry of the site's Packages tree, and five contracts state their description by @willemkokke
  • The tool store's table, lock and verbs take toolroom's name, and the store ships the table's schema and its own reader by @willemkokke

[0.2.0] - 2026-10-07

Added

  • Ruff runs as its own extension, a birth finishes in the newborn's own fm, and the local loop tests an extension before its release by @willemkokke
  • Every distribution root declares its public names in its init.py and serves what need not load on first use, and the api modules go by @willemkokke

Fixed

  • One process at a time supplies a tool version: a second supply waits for the first and finds it present, and a view record retired mid-read is left out instead of crashing the probe by @willemkokke

[0.1.0] - 2026-10-04

Added

  • The host allowance for store tools: a tool on PATH serves when allowed and satisfying, the store installs otherwise by @willemkokke
  • Examples are files: a package's examples live under docs/examples/ as python files a page includes by snippet, and one harness runs each through the kind's runner, replacing footman's page-as-session harness and its three markers by @willemkokke
  • Every distribution root is a namespace whose public names live in its api module, and the docs layer moves to livery.extensions.docs by @willemkokke
  • Spec and Scope parse the one requirement grammar, name[options]?>=floor@scope, and Requirement parses through them by @willemkokke
  • A tool requirement takes ? and !: an optional tool is locked where it can be served and never refused, and a plugin declares the tools its verbs need by @willemkokke
  • Git LFS is a workspace setting: extensions ship LFS rules, composed while [workspace] lfs is on and named while it is off, with a git_lfs record, its hooks and LFS checkouts in CI by @willemkokke
  • The copier answers move into workshop.toml: identity in [workspace], members from discovery with their own description, dev-extras and template, and the answers files go by @willemkokke
  • Tasks.py and each package's cliff.toml are composed by the fragment engine, so copier only births by @willemkokke

Fixed

  • Tools.artifacts refuses a record that does not load in one line naming the file, and the layout refusal says to list the host first by @willemkokke

Changed

  • A verb that reaches no forge and no tool store loads neither: the forge, store and strongroom roots serve their names on first use, and the workshop and the bench import the store where they use it by @willemkokke

[0.0.0] - 2026-09-29

Added

  • The tool store is born with its spec model and its home by @willemkokke
  • The engine installs a pinned tool from its spec into the store by @willemkokke
  • The release act, the points by hand and the clock on GitLab: the loop is whole on both lanes by @willemkokke
  • The tool record, and total resolution by @willemkokke
  • Annotated entry points, and one tree digest everywhere by @willemkokke
  • The surface rides in the record, and the histories are absorbed by @willemkokke
  • The three declaration sites, the catalogue, and the lock by @willemkokke
  • Receipts, materialisation on sync, and the modes by @willemkokke
  • The stubs live in typings/, written from the index, and the toolroom wheel ships none by @willemkokke
  • The steady state costs the stats: a nothing-moved gate, records digested once, a lazy catalogue by @willemkokke
  • The store renders stubs from surfaces, and the index holds none by @willemkokke
  • The record is one file per tool with one line per option by @willemkokke
  • Ingest verification, the nine structural checks over every host by @willemkokke
  • The refresh records each new version's artifacts per host, and an archive root may carry the version by @willemkokke
  • Basedpyright comes through bun: the store supplies bun-install, and bun is its locked dependency by @willemkokke
  • The sidebar's machine sections are marker blocks the author may place, and land in a fixed order otherwise by @willemkokke
  • A tool's own switches live in its record's env, and gh's update check leaves the code for the record by @willemkokke
  • The store owns download, unpack and the host table; the bench reads through it and runs a release binary in its own tree by @willemkokke
  • An npm kind names its runtime, node has a record from nodejs.org, and basedpyright runs on node by @willemkokke
  • The extension compiles against the library at HEAD and a third-party package through the store's cmake-conan provider, and the store's downloaded kinds are one download by @willemkokke
  • The pypi and python kinds name their source; uv is the installer, not the kind by @willemkokke
  • A tools ref follows the record's layout for its version, and cmake's view drops its docs and GUI by @willemkokke
  • The lock names a delegated tool's resolved graph, and fm tools.lock writes it by @willemkokke
  • A delegated tool installs the graph the lock pins, resolving nothing and checking every artifact by @willemkokke
  • A managed file carries the regions the repository owns by @willemkokke
  • The dotnet kind: .NET as a runtime record on every host, NuGet tools through it, pwsh as a download by @willemkokke
  • Host-scoped tool requirements: a tool required on some hosts alone by @willemkokke

Fixed

  • An origin that does not answer is a store refusal, not a raw exception by @willemkokke
  • A system-check tool is held to the record's floor alone, not the locked version by @willemkokke
  • A system tool is held to the highest of the record's floor and the sites' floors, and the site is named by @willemkokke
  • A bun global install gets its own project under the tool's directory, where bun's walk up for one stops by @willemkokke

Changed

  • The contract key type becomes kind by @willemkokke