Repository navigation
Release 5.1.1: unify the version across npm and the pip code tier - #58
Merged
Merged
Conversation
Bumps the release version 4.4.36 -> 5.1.1 (lib/version.js + package.json), the single source of truth, so npm and the pip code tier (already 5.1.1) line up on one number. PROVENANCE (V4.4n32), FORMAT (4.4) and the engine id are unchanged, so cited benchmark numbers stay valid. Updates CITATION.cff, the README launch line and the CHANGELOG top entry (the three version surfaces verify checks), and raises the rollback test's sentinel newer-version from V4.5 to V99.0 so it stays above the release. npm run verify 916/0.
amin-rigi
previously approved these changes
Oct 6, 2026
daidocs.js had CRLF in the Windows working tree where MANIFEST.sha256 was generated, so its hash did not match the LF content a fresh (CI) clone checks out: npm run verify failed with '1 of 351 differ' on Linux/macOS/Windows runners. Converted it to LF and regenerated the manifest. verify 916/0.
CI runs npm install before npm run verify. package-lock.json is in MANIFEST.sha256, so leaving it at 4.4.36 made CI's npm install rewrite its version to 5.1.1, changing its hash and failing the manifest check on every runner. Bumped the lock's version to 5.1.1 (format otherwise untouched, so npm install stays a no-op) and regenerated the manifest. verify 916/0.
amin-rigi
approved these changes
Oct 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the release version 4.4.36 → 5.1.1 so npm (
daidocs) and the pip code tier(
kerneta-cai, already 5.1.1) line up on one number. After this merges and both packagespublish, everyone sees 5.1.1.
Changes
lib/version.jsVERSIONandpackage.jsonversion→5.1.1(the single source oftruth that every surface imports).
npm run verifyenforces:CITATION.cff(version +date-released), the README launch line, and the CHANGELOG top entry(
## [5.1.1] - 2026-10-06, with the Kerneta-Cai code-tier note).V4.5→V99.0) so it stays abovethe release version after the major bump.
Deliberately unchanged
PROVENANCE(V4.4n32),FORMAT(4.4) and the engine id stay as they are, so everycited benchmark number and document remains valid.
Verification
npm run verify916/0. No engine or behaviour changes, version metadata only.