Every Progmasoft-authored file moves from MPL-2.0 WITH AdditionRef-Progmasoft-Exception-2.0 to LGPL-3.0-or-later, from 0.5.0 on. Catch2-originated files keep BSL-1.0, and the vendored yyjson and pugixml keep MIT. - LICENSES/ holds the LGPL-3.0 text and the GPL-3.0 text it builds on, both as published by the FSF; the MPL-2.0 and Progmasoft Exception texts go, since no file uses them any more. - Five files that came from Catch2 and were rewritten by Progmasoft (.clang-format, the issue and pull request templates, SECURITY.md) keep Catch2's notice next to Progmasoft's and say LGPL-3.0-or-later AND BSL-1.0. - //tools:check expects the new header of Progmasoft files; the amalgamation notes say LGPL-3.0-or-later and the amalgamated files are regenerated; meson's project license is BSL-1.0 and LGPL-3.0-or-later. - README gains a License section; LICENSES/README.md, contributing.md and progmasoft-catch3.md describe the new split and that releases before 0.5.0 keep the license they were published under. Every commit to Progmasoft's files since the fork is the maintainer's. Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
NextPatch added one to the patch without a check, so a patch at std::numeric_limits<unsigned>::max() wrapped to 0 and --next would have moved the version back. It returns nothing there now; tests cover a three- and a four-number version at the limit. Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
Progmasoft repositories use Semantic Versioning since 2026-11-12, but //tools:version still knew the four-number counters: given 0.4.0 it wrote 0.4.0.0 everywhere, and --next stepped the fourth number. - A Version is three numbers; ParseVersion takes exactly three, without leading zeros, and FormatVersion writes three. - --next is the next patch release. It also follows a four-number version as the rule says: the fourth number goes and the patch rises, so 0.3.0.2 is followed by 0.3.1. - ReleaseNotesOf finds a section by the version it was published as. Its fallback for "D = 0" read the fourth element of what is now a three-element array; it is gone. - Tests for the new parsing, NextPatch and release-note lookup; docs/contributing.md and the tool's usage say what the tool does. Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
repo_info starts Git in the checkout with fixed commands, so a shell never reads a path, reports an unknown state as null rather than clean, and counts only files it can start. third_party reads every archive before it changes a file and refuses two modes. version checks that the sources make a distribution, computes every place before writing any, and release_notes finds a three-number heading for a version with D = 0.
The scripts in use become programs run with `bazelisk run //tools:<tool>`,
and arguments follow `--`:
amalgamate the single-file distribution; --check only compares it
check licenses, convenience headers, header guards, file names,
versions and whether the distribution is up to date
third-party compares third_party/ with its archives, or writes it
version prints the version, or moves every place that states it
release-notes prints a section of the release notes
repo-info reports the checkout and the tools on PATH; --json writes
it through yyjson, with the fields of Tala's repo-info
amalgamate writes what the Python script wrote, byte for byte, except for
the time of generation. That line is gone so that the output is
deterministic and --check can compare it.
MODULE.bazel now pins the archives of third_party/ by version and sha256,
so Bazel fetches and checks them instead of a tool of ours, and Renovate
reads the versions there.
Scripts nobody used are gone: fixWhitespace, updateDocumentSnippets,
buildAndTest, and updateDocumentToC, which rewrote unrelated documents.
CheckConvenienceHeaders leaves CTest, since //tools:check runs it in CI.
The Python of tests/TestScripts stays: those are tests, not tools.