Skip to content

chore(deps): bump lua-pure to v0.1.2, raise Go to 1.25#7

Merged
htcom-code merged 1 commit into
mainfrom
chore/lua-pure-0-1-2
Jul 5, 2026
Merged

chore(deps): bump lua-pure to v0.1.2, raise Go to 1.25#7
htcom-code merged 1 commit into
mainfrom
chore/lua-pure-0-1-2

Conversation

@htcom-code

Copy link
Copy Markdown
Owner

Why

lua-pure released v0.1.2, which raises its own toolchain to go 1.25.11 (was 1.24). Because a dependency's go directive is a floor for consumers, go-lua-perf must move to Go 1.25 to keep using lua-pure.

Change

  • go.mod: lua-pure v0.1.1 → v0.1.2; go 1.24.6 → 1.25.11 (auto-raised by go get to satisfy the dependency).
  • User-facing requirement docs synced to Go 1.25+ / lua-pure v0.1.2: README badge + summary line (en + ko), CONTRIBUTING.
  • CHANGELOG [Unreleased] entry (en + ko).

Left as historical records (unchanged): the released [0.0.1] changelog entry and the docs/BENCHMARKS.md "measured on Go 1.24" note.

Verification (local, go1.25.11)

  • go build ./..., go vet ./..., go test ./... — all pass
  • gofmt -l . clean · govulncheck ./... exit 0

Note

The GOTOOLCHAIN=auto workaround added for the govulncheck job is now technically redundant (the pinned toolchain is already ≥ 1.25), but it is harmless and left in place.

- lua-pure v0.1.2 pins go 1.25.11, so consumers must be >= 1.25;
  go.mod go directive moves 1.24.6 -> 1.25.11 to satisfy it
- sync user-facing requirement docs (README badge/summary en+ko,
  CONTRIBUTING) to Go 1.25+ and lua-pure v0.1.2
- record the bump under CHANGELOG [Unreleased] (en+ko); v0.0.1 and the
  benchmark measurement note stay as historical records

#deps #luapure #gotoolchain

Co-Authored-By: htjulia <htjulia1@gmail.com>
@htcom-code htcom-code merged commit 38bd982 into main Jul 5, 2026
7 checks passed
@htcom-code htcom-code deleted the chore/lua-pure-0-1-2 branch July 5, 2026 13:43
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