Prepared 2026-11-18. The tag v2.1.0 is pushed by the owner; the release workflow then builds, signs
and publishes the archives (release signing).
Proposed tag message:
Lesscode 2.1.0: a fix for a kill on Linux that could end all of a user's processes; call edges across files (
measure-scope); a bounded comparison of two versions with a solver (bound-check)
- On Linux, a command that ran over its time limit could take every process of the user with it.
deconvolute runandstep checkstop a command that exceeds its limit, and one that is running when you interrupt them, withkill -KILL -<group>. Thekillprogram of procps 4.0.2 (Debian 12) reads a group number that starts with 1 as-1, which means every process the user may signal. The call now ends its options with--. Releases 1.1.0 to 2.0.0 have the fault. Whether it strikes depends on the process number, so a run can pass many times before it does. If you use one of those releases on Linux, update.
deconvolute measure-scopelists which functions of a set of files call which, by name, for Python, TypeScript, Java and Rust.deconvolute analyzenow also reports the calls a file makes to functions it declares. Each language pack names its call nodes; a pack of your own without that entry still loads and its calls are not counted. Guide: the agnostic driver.deconvolute bound-checkasks whether two versions of a piece of behaviour can differ inside ranges you state. You give it a target file with the symbols and their ranges and, per version, an SMT-LIB expression and a command. A solver you supply, pinned by its hash, says whether the two expressions can differ. Every case in the ranges is also run through both commands, and a difference the solver finds is run again. It works for any language, because you write the expressions.- Two worked examples of state that was spread over several places and is one state machine now: examples. One is made up as an introduction; one is from a remote desktop client.
lesscode-model checkandmeasureno longer accept a reply that was cut off or that the model refused, whatever its text says. Before, only the text was judged. Ameasureresult can therefore be lower than the same task set gave under 2.0.0.- If you build on the
lesscode-modelcrate: the check you hand towith_repairsreceives the whole reply, not its text alone. - Everything else is as in 2.0.0. Receipts keep their form.
- Linux, in the project's container pipeline, at the commit with the fix: 408 of 408 tests of the
core and 85 of 85 of
lesscode-model, format, lints and budgets clean. The same pipeline was killed four times before the fix, each time at the test that makes a command run over its limit. - Windows: the core's suite, format and lints.
bound-check: one case of this project's experiments, a row filter in two versions. The solver found no difference for the correct candidate and all 81 cases agreed; for a planted fault it found one, 18 of 81 cases differed, and the solver's case was reproduced.measure-scopeand the call counts: for Python they equal a frozen reference on six sets of files of the experiments. For the other three languages they are covered by tests on small sources.
Not tried: macOS and the two ARM targets were not run before this preparation; the hosted pipeline
runs them when main is pushed. The kill fix was confirmed against procps 4.0.2 only.
- No command in this release finds a state machine. The two examples were consolidated by hand; a research program named the places in one of them. See the research log, R156 to R160.
bound-checkcompares the expressions you wrote. It does not check that an expression describes its code; running every case through the commands is what ties the two together, and only inside the ranges.measure-scopematches calls by name. Two functions of the same name are not told apart.analyzedoes not count the arms of a Rustmatchas conditions.
- Push main and wait for the pipeline: green on all five platforms.
- Set
date-releasedinCITATION.cffto the day of the tag if it is not 2026-11-18. git tag -a v2.1.0 -m "<the tag message above>"andgit push origin v2.1.0.- Approve the
releaseenvironment when the workflow asks. - After publication: check signatures, checksums and the attestation for all ten archives, and that Zenodo archived it.
- Consider a note on the 1.1.0 to 2.0.0 release pages that points Linux users to this release.