Skip to content

fix(lua): update go-lua with checker and signed-zero fixes - #1081

Merged
wolfy-j merged 1 commit into
mainfrom
chore/go-lua-stable-fixes-20261114
Nov 14, 2026
Merged

wolfy-j merged 1 commit into
mainfrom
chore/go-lua-stable-fixes-20261114

Conversation

@wolfy-j

@wolfy-j wolfy-j commented Nov 14, 2026

Copy link
Copy Markdown
Contributor

Updates go-lua from v1.7.1 to v1.7.2-0.20261114153118-f8366a939c0e, pinning the merged commit containing:

  • go-lua #84: recursive-table inference converges, while sibling fields retain separate identities.
  • go-lua #86: guard exclusions apply to the exact guarded path, preventing exclusions from leaking into other fields.
  • go-lua #87: boxed floating-point values and compiler constants preserve -0.0. Numeric zero table keys still share the integer key 0.

The dependency uses Go's immutable pseudo-version because these commits do not yet have a release tag. The diff contains only go.mod and go.sum.

Validation passed against the downloaded dependency:

  • Runtime Lua and Lua boot-component suites: go test -short -timeout 10m -tags 'fts5 sqlite_vec sqlite_preupdate_hook' ./runtime/lua/... ./boot/components/runtime/lua/...
  • CLI lint regressions: go test -short -timeout 5m -tags 'fts5 sqlite_vec sqlite_preupdate_hook' ./cmd/wippy/cmd -run 'TestLint|TestBoundedLintWorkers|TestDefaultLintWorkers'
  • Upstream go-lua full suite, focused race tests, vet, and all 12 CI checks passed for the corrected Add Wippy icon into Readme and IDEA metadata #84 head; EE2-1757 WIP. restore test coverage #86 and dependencies demo #87 also passed all 12 checks before merging.

@wolfy-j
wolfy-j requested a review from skhaz November 14, 2026 15:57
@wolfy-j
wolfy-j merged commit 5984853 into main Nov 14, 2026
21 checks passed
@wolfy-j
wolfy-j deleted the chore/go-lua-stable-fixes-20261114 branch November 14, 2026 16:31
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.

2 participants