Skip to content

ci: pin libtaurus to v0.25.0 - #10

Merged
ronaldtse merged 1 commit into
mainfrom
chore/pin-libtaurus-v0.25.0
Aug 18, 2026
Merged

ci: pin libtaurus to v0.25.0#10
ronaldtse merged 1 commit into
mainfrom
chore/pin-libtaurus-v0.25.0

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

Summary

  • .github/workflows/build.yml: pin libtaurus v0.22.0 → v0.25.0
  • README.adoc: update the CI pin note

Verification

  • Header diff v0.22.0 → v0.25.0 over src/include/ is empty — the entire serialize/parse/mutation campaign (text-heavy serialize 3×, append 300×, XPath up to 87× vs pugixml, depth-limit removal) was internal. No FFI declaration changes.
  • Local suite against a v0.25.0 build: 176/176 passing.
  • Benchmark sweep against v0.25.0: Taurus ahead of Nokogiri on every op — traverse 1.57×, serialize 2.86×, xpath union 2.28×, xpath complex 1.09×.

Notes

Test plan

  • CI green on Linux + macOS (Ruby 3.3/3.4/4.0)
  • Windows failures match the known #278 signature
  • After merge: trigger release (next_version=patch) for v0.1.3

Public headers are byte-identical v0.22.0 -> v0.25.0; the serialize/
parse/mutation campaign (text-heavy serialize 3x, append 300x, XPath
up to 87x vs pugixml) was all internal. No FFI declaration changes.

Local verification against v0.25.0: 176/176 specs, and the full
benchmark sweep stays ahead of Nokogiri on every operation
(traverse 1.57x, serialize 2.86x, xpath union 2.28x).
@ronaldtse
ronaldtse merged commit 1d5561f into main Aug 18, 2026
9 of 12 checks passed
@ronaldtse
ronaldtse deleted the chore/pin-libtaurus-v0.25.0 branch August 18, 2026 00:13
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