Skip to content

Upgrade ladybug 0.19.1 - #36

Merged
adsharma merged 3 commits into
LadybugDB:masterfrom
JohnTStotko:upgrade-ladybug-0.19.0
Aug 7, 2026
Merged

Upgrade ladybug 0.19.1#36
adsharma merged 3 commits into
LadybugDB:masterfrom
JohnTStotko:upgrade-ladybug-0.19.0

Conversation

@JohnTStotko

Copy link
Copy Markdown
Contributor

Summary

  • Bump @ladybugdb/core and @ladybugdb/wasm-core from 0.18.0 to 0.19.0 so Explorer is compatible with databases created by Ladybug v0.19.0.
  • Regenerate the Cypher ANTLR parser (src/utils/CypherParser/*) against the v0.19.0 grammar
  • Fix generate-grammar to invoke antlr4ng directly instead of the now-deprecated antlr4ng-cli (the latter has been unmaintained since Feb 2025 in favor of antlr-ng).

Validation

  • Rebuilt the Docker image and ran it against a database created via the Python v0.19.1 PyPi package, to confirm compatibility with the 0.19.x on-disk format.
  • Verified the auto-complete works for new grammar introduced in LadybugDB/ladybug@f1d8e26; ALTER TABLE Foo SET SORTED BY (bar DESC) highlights and executes correctly

Bump @ladybugdb/core and @ladybugdb/wasm-core from 0.18.0 to 0.19.0.
antlr4ng-cli is deprecated, so switch generate-grammar to invoke
antlr4ng directly, then regenerate the checked-in parser against
the 0.19.1 grammar.
@adsharma
adsharma force-pushed the upgrade-ladybug-0.19.0 branch from 673fec1 to 5c9ea9d Compare August 6, 2026 15:49
@adsharma adsharma changed the title Upgrade ladybug 0.19.0 Upgrade ladybug 0.19.1 Aug 6, 2026
@adsharma

adsharma commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Just realized that 0.19.1 didn't make it to npmjs because of an error in the build pipeline. Rerunning it now.

@adsharma
adsharma merged commit f257d5a into LadybugDB:master Aug 7, 2026
1 check passed
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