Skip to content

chore: re-vendor bitn.lua from lua-bitn v0.6.5 - #18

Merged
derek-miller merged 1 commit into
mainfrom
claude/revendor-bitn-v0.6.5
Oct 17, 2026
Merged

derek-miller merged 1 commit into
mainfrom
claude/revendor-bitn-v0.6.5

Conversation

@derek-miller

Copy link
Copy Markdown
Contributor

vendor/bitn.lua is now the lua-bitn v0.6.5 release asset, copied verbatim. That asset is byte-identical to a local make build of the tag (sha256 3c7f97e539617afc800926ee31186b0d53b3bd8b97292e65a694a96ee645fccd).

bitn v0.6.5 is v0.6.4 plus two CI-only changes: finitelabs/lua-bitn#24 (runner pin) and finitelabs/lua-bitn#25 (action and tool pin bumps, Lua 5.5 added to the test matrix). Neither touches src/, so the only diff here is the embedded VERSION stamp, v0.6.4 → v0.6.5. Tests build against the vendored file, so CI exercises it.

Verified locally: make check, ./run_tests.sh all on LuaJIT 2.1 and Lua 5.5.1 (16/16 each, including the lpack module), and make build (core and portable).

Not tagging on merge. The OpenSSL bignum work (branch claude/openssl-big-number-support-2a0c40) is about to change this library. The next lua-crypto release waits for it, so lua-noiseprotocol only has to roll crypto out once.

@svc-finitelabs svc-finitelabs Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified at 40f2ccf: vendor/bitn.lua is byte-identical to the lua-bitn v0.6.5 release asset (sha256 3c7f97e5...), and the main copy is byte-identical to the v0.6.4 asset, so the only change is the VERSION stamp on line 3571. v0.6.4...v0.6.5 is #24 and #25, touching only .github/workflows/, CLAUDE.md and README.md. CI green across all 12 jobs, including Lua 5.5 and the three lua-openssl versions.

@derek-miller
derek-miller merged commit 823c23a into main Oct 17, 2026
12 checks passed
@derek-miller
derek-miller deleted the claude/revendor-bitn-v0.6.5 branch October 17, 2026 20:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant