1.0 RC3 - Jeff Buckley

This one is a huge (overdue) release! ⌛ 😅
At the time of writing, this release alone comprises almost 61% of Liquigraph commits (❗).

Special thanks come to @sim51, @jcgay, @mvitz, @pointwisefixed and last, but not least, @fpavageau for their valuable contributions! 👍

You can also try the brand new Homebrew recipe!

Let's now review the most significant improvements:

• Issue #33: Liquigraph client has been entirely rewritten and repackaged. No more Python needed for Windows users, just a plain old JDK 😎
• Issue #8: The changelog can now include "sub-changelogs" (recursively):

<?xml version="1.0" encoding="UTF-8"?>
<changelog xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://liquigraph.org/schema/1.0-RC3/liquigraph.xsd">
    <!-- import "sub-changelogs"-->
    <import resource="version_1/sub_changelog.xml" />
    <import resource="version_2/sub_changelog.xml" />
    <!-- and/or define directly changesets-->
    <changeset [...] /> 
    <!-- [...] -->
</changelog>

• Issue #10: Liquigraph now has a well-defined XML schema (yeah, previous snippet spoiled it 😞)
• Issue #40: Liquigraph metadata queries now run in a separate transaction from the user-defined migration queries
• Issue #44: Changesets can now define more than 1 query

There have been some invisible improvements such as the use of Docker 🐳 to test Liquigraph executions against remote Neo4j instances (#59)! 🤘

Breaking change

The metadata graph has now the following structure (^ denotes cardinality):

(__LiquigraphChangelog)^1 -[:EXECUTED_WITHIN_CHANGELOG {time}]-
(__LiquigraphChangeset {id,author,checksum})^1..n -[:EXECUTED_WITHIN_CHANGESET {order}]-
(__LiquigraphQuery {query})^1..n

Aforementioned issue #40 also brings a (__LiquigraphLock {name}) node to the family! 👶

Enjoy and grab it while it's hot! 🔥