Repository navigation
Releases
ict edited this page Oct 16, 2026
·
1 revision
Versions are MAJOR.MINOR.PATCH: MAJOR for incompatible changes (protocol,
move/board format, interface), MINOR for new features or measurable changes in
strength or behaviour, PATCH for fixes. The version lives in src/version.h
and is reported over UCI on the id name line.
| version | change | measured |
|---|---|---|
| 1.0.0 | first release — the engine | — |
| 1.1.0 | king safety (pawn shield) | +50 Elo |
| 1.2.0 | pawn structure (passed, doubled, isolated) | +35 Elo |
| 1.2.1 | fix elapsed_ms 32-bit overflow |
bugfix |
Each release is tagged vX.Y.Z with a source tarball on the
releases page.
- Bump
src/version.hand add aCHANGELOG.mdentry. - Commit; tag
vX.Y.Z; push the branch and the tag. - Build the tarball with
git archiveand attach it to a GitHub release. - Rebuild on the target machine (XL C) and run
make check. - Update the project site — version, download link, and any figures the change affects. (Learned the hard way: a stale page outlives the release.)