Skip to content

Changelog

All notable changes to livery-extensions-pytest 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.1.0] - 2026-10-17

Added

  • A check names the package-level extensions whose packages it judges instead of package kinds, and a kind stands for what a package that lists none holds by @willemkokke
  • [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
  • The coverage extension draws every language's pages from parts in the line format with a renderer of its own, and pytest reduces coverage.py's arcs to those parts by @willemkokke
  • The coverage machinery leaves the base for the coverage extension, so a workspace that does not list coverage runs no coverage leg by @willemkokke
  • Pytest and cmake measure for coverage through their [for.coverage] tables, so a workspace without coverage runs its tests unmetered, and coverage with nothing that measures is dormant and named by @willemkokke
  • The coverage record stores parts in the line format with each file's fixed facts once, the union merges them without coverage.py's commands, and llvm-cov's counted ranges reach the pages by @willemkokke
  • Every coverage row names the tests that reached each line, numbered once so a test keeps its index across runs and legs by @willemkokke
  • The docs extension declares a docs phase and a deploy phase, and the task reference, the package generators and coverage's pages become their steps by @willemkokke
  • The python extension judges each source's imports against its package's declared dependencies, and holds the terminal rule 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
  • Package.kind goes, public_modules and compile_commands leave the workshop's public names, and a step's kinds refuses naming extensions by @willemkokke
  • The agent's guidance gives each installed extension a block read from its declaration, and the kit holds every declaration to its docs by @willemkokke
  • A shard runs its share of the tests by @willemkokke

Fixed

  • The rendered pytest.toml keeps only a failed test's tmp_path, so a session ends at its last test instead of deleting an older session's whole temp tree by @willemkokke
  • A catalogue, a contract and the task tree are read once per process, a locked sync judges the tool lock once, and coverage omits pytest's temp trees by @willemkokke
  • Coverage writes each set of test indexes as digits and commas, in version 3 of the line format, so no store push holds a token shape GitHub's push protection refuses by @willemkokke
  • The shard record names its suites by @willemkokke
  • A file has one shard whatever run of the test step reaches it by @willemkokke

Changed

  • The tool extensions sit inside the workshop's entry of the site's Packages tree, and five contracts state their description by @willemkokke
  • Every extension declares its steps as [phases..] with main, fix and safe-fix placing their paths and arguments, the lifecycle phases name their extension, listed-with is enabled at the step's address, and the package option tables follow by @willemkokke
  • The check tables refuse naming the step spelling: the transition reader goes with placed, narrowing, transport, threshold, roles, listed-with, options, judge, run and arguments as keys, the transports and the further roles, and [for.] carries every table by @willemkokke
  • Slots, contributions, editor-extension and release-notes are declared queries with a combine rule, declared by the base in its contract file and by extensions, answered by the listed extensions in list order; the slots module and the release-notes registration go by @willemkokke
  • The lifecycle phases and the gate share one walk: every step is a footman step inside parallel(), a package step once per package, ordered by after and by provides and reads; pre and post go, every step reads into the one record and DeclaredPhase goes, and GateContext folds into PhaseContext by @willemkokke
  • The train takes isolated and configuration: a step serves the side of its phase it declares, the test phase's isolated side runs once per resolution [release] prove lists, replay is verify, and a bare fm build and fm run build debug while the gate instruments by @willemkokke
  • The names: StepRecord, _steps.py, register_step and the public step_option say step and phase, PhaseContext.step names the running step, and role is gone by @willemkokke
  • This repository's packages list their extensions by @willemkokke
  • Pytest runs the suites and examples through runners the python extension answers, and run_suites and kind_examples leave the public names by @willemkokke
  • The in-wheel extensions call the workshop's public names where one exists by @willemkokke
  • Every extension is one kind: an extension declares no levels, either list takes any extension, and the installed set is the root's set and every package's set by @willemkokke
  • The workspace's own tests hold the root's set, so a root whose set holds no python runs none of them and says why, and fm new.project's stock list names python by @willemkokke
  • A root entry's without names the targets its extension contributes nothing to, in place of for, so cooperation stays greedy and fm extensions prints what each entry leaves out 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
  • The cmake extension leaves the workshop's wheel for livery-extensions-cmake, and a test edge renders into the package's test extra by @willemkokke
  • The docs extension leaves the workshop's wheel for livery-extensions-docs by @willemkokke
  • The coverage extension leaves the workshop wheel for its own distribution, livery-extensions-coverage, taking Pygments with it by @willemkokke
  • Python reads public names alone: the source records, the reference map, the graph widening, a venv's paths and the example and speed names join the workshop's API, python's upload moves into python, and the dev act publishes through each member's publish phase by @willemkokke
  • Python leaves the workshop wheel, which now ships the base alone by @willemkokke

[0.0.0] - 2026-10-07

Added

  • Pytest runs as its own extension, configured by the root pytest.toml and .coveragerc, and the python kind's test runner collects only the packages it is handed by @willemkokke
  • A check's own verb hands the tool it wraps the words after --, and fm check and the role verbs refuse them, naming the verbs that take them 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
  • Every extension declares itself in extension.toml, read at mount without importing it, and the check records leave the public names by @willemkokke

Changed

  • Footman's internal modules are private, every public module under a root is its api or declared there, and other packages' sources reach footman through its api by @willemkokke