chore: release v0.5.0

[github-actions]

🤖 New release

• cql2: 0.4.2 -> 0.5.0 (✓ API compatible changes)
• cql2-cli: 0.4.2 -> 0.5.0 (✓ API compatible changes)

Changelog

cql2

0.5.0 - 2025-12-08

Added

• add str and repr (#122)
• add version to python module (#121)

Fixed

• (ci) remove locked check (#125)
• it wasn't used anywhere and it was broken (#124)
• (ci) update to latest npm for publishing
• (ci) remove clean install from npm publish

Other

• use release bot for releasing (#145)
• (deps) bump the production-dependencies group across 1 directory with 3 updates (#144)
• fix ci config (#143)
• (deps) bump the production-dependencies group with 3 updates (#142)
• add release-plz workflow (#140)
• (deps) bump the production-dependencies group with 6 updates (#138)
• (deps) bump actions/checkout from 5 to 6 (#134)
• try groups (#136)
• group dependencies (#135)
• (ci) actually keep the locked check (#127)
• (deps) bump actions/setup-node from 4 to 6 (#126)
• (wasm) [breaking] Make WASM module interface more like Python module (#120)
• update cargo lock

Changed

• Normalized WASM interface to match Python API (#120)
  • Renamed CQL2 to Expr for consistency with Python
  • Changed Expr.matches() and Expr.reduce() to accept JS objects instead of strings
  • Changed Expr.to_json() to return JS objects instead of strings

cql2-cli

0.5.0 - 2025-12-08

Other

• (wasm) [breaking] Make WASM module interface more like Python module (#120)

---

This PR was generated with release-plz.

[alukach]

I'm a little confused about what's going on here. Our CLI has its own CHANGELOG but it contains only a subset of the changes from the main CHANGELOG? That seems cool, however the change mentioned in the CHANGELOG is not actually relevant to the CLI, as far as I can tell

[gadomski]

Yeah, this is due to a single commit hitting files in the cli repo (specifically this auto-format: https://github.com/developmentseed/cql2-rs/pull/120/files#diff-c1f8f7498da827a634bddc8a7559198bc99b296e9d9e8b91a70b503662995b8c). I think if we're careful with our commit/PR blast radii in the future, the changelogs will auto-render better.