catch3, branch docs/no-former-language Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Merge branch 'devel' into docs/no-former-language 2026-11-15T10:53:40+00:00 Leitwolf 2026-11-15T10:53:40+00:00 9ea8d3a88334d62711f3e9aa429c7fe4905f2ef0 






Merge pull request #43 from Progmasoft/release/catch3-0.4.0
2026-11-15T10:53:29+00:00

Leitwolf

2026-11-15T10:53:29+00:00

8979c1caf2eee321cf497671805d2177980c421e

Release Catch3 0.4.0




Release Catch3 0.4.0






Allow the anchors and line breaks of the documents in markdownlint
2026-11-15T09:22:19+00:00

Leitwolf11

2026-11-15T09:22:19+00:00

74df225e5d893a07e7bf07f0d82eea580507489b

The documents keep Catch2's style, an anchor at the top of each page and
a contents list whose lines end in <br>; Codacy's markdownlint reported
the new contents line of the release notes as inline HTML.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1





The documents keep Catch2's style, an anchor at the top of each page and
a contents list whose lines end in <br>; Codacy's markdownlint reported
the new contents line of the release notes as inline HTML.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1







Release Catch3 0.4.0
2026-11-15T09:17:43+00:00

Leitwolf11

2026-11-15T09:17:43+00:00

6f4d3fa3328d6fb78f9a41f45282c11758872c9c

Every place that states the version says 0.4.0, written by
bazelisk run //tools:version -- 0.4.0, and the single-file distribution
carries it. The release notes describe the release: per-test coverage
with --coverage, secret-looking variables withheld from workers unless
--pass-env names them, the repository tools in C++17 under Bazel, and
versions with three numbers again.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1





Every place that states the version says 0.4.0, written by
bazelisk run //tools:version -- 0.4.0, and the single-file distribution
carries it. The release notes describe the release: per-test coverage
with --coverage, secret-looking variables withheld from workers unless
--pass-env names them, the repository tools in C++17 under Bazel, and
versions with three numbers again.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1







Merge pull request #41 from Progmasoft/fix/version-tool-semver
2026-11-15T09:15:51+00:00

Leitwolf

2026-11-15T09:15:51+00:00

ac438d0c34d89e14d51aebe3b0314c7e38000bb8

Number versions MAJOR.MINOR.PATCH in the version tool




Number versions MAJOR.MINOR.PATCH in the version tool






Drop references to the former compiler from two comments
2026-11-15T09:07:30+00:00

Leitwolf11

2026-11-15T09:07:30+00:00

13ecce487c3075e4ccc2f62b9c08597459d1a268

The macOS workflow and RepositoryReport.hpp explained themselves by another project; they now say what they do: macOS gets one job, and the JSON report uses the field names of RepositoryReport in camelCase.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1





The macOS workflow and RepositoryReport.hpp explained themselves by another project; they now say what they do: macOS gets one job, and the JSON report uses the field names of RepositoryReport in camelCase.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1







Refuse a next patch past the largest number
2026-11-14T19:42:54+00:00

Leitwolf11

2026-11-14T19:42:54+00:00

e2905c736cf2e36965c071c21bc7911eb3c59a7b

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





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







Number versions MAJOR.MINOR.PATCH in the version tool
2026-11-14T19:03:45+00:00

Leitwolf11

2026-11-14T19:03:45+00:00

2d21d2e0f9c6e0789e9c55d6cba611234dc61a60

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





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







Merge pull request #39 from Progmasoft/feature/per-test-coverage
2026-11-14T13:46:04+00:00

Leitwolf

2026-11-14T13:46:04+00:00

94a996a3ceafa9f0004ffc28a7de5c543cdb51c2

Keep per-test coverage with --coverage (roadmap step 4)




Keep per-test coverage with --coverage (roadmap step 4)






Make the start lock a never-destroyed object
2026-11-13T21:56:32+00:00

Leitwolf11

2026-11-13T21:56:32+00:00

5ad02bccfcb925df02d1273901b6e248d477c5fa

A function-local static std::mutex has an exit-time destructor, which
the macOS build rejects with -Wexit-time-destructors. The lock is now
allocated once and never destroyed, which also keeps it usable by a
thread that starts a child while the process exits.





A function-local static std::mutex has an exit-time destructor, which
the macOS build rejects with -Wexit-time-destructors. The lock is now
allocated once and never destroyed, which also keeps it usable by a
thread that starts a child while the process exits.