There are releases in this log that exist to move a version number. This is one of them.
Pengy ships as three implementations of one contract: the Python package, pengy-rs (Rust, with a
shared Rust core), and PengyCPP. They release on their own schedules, and the version number is
meant to mean the same thing in all three: 1.8.4 is the same contract everywhere. When one edition
moves ahead, the numbers stop meaning that, and the way to fix it is a release that changes nothing
except the number.
1.8.5's own notes say it: "Version bump to keep all three Pengy editions in lockstep. No functional change." The commit is 2 files, 4 insertions, 3 deletions.
The reason this is a post and not skipped: a version number you can rely on across editions is a
feature. The Rust edition implements the C++ spec; the contract is documented in docs/API_SPEC.md
and the cross-edition parity spec; a test suite (169 tests) runs against the Python implementation
and the Rust CLI, and the C++ edition re-verifies with its own test target. When the numbers are in
step, "which version am I running" has one answer, and when they are not, a bug report from a C++
user and a fix from the Python tree are not talking about the same thing.
The next release, 1.8.6, is the large coordinated CLI release that this bump cleared the way for.