Skip to content
This repository has been archived by the owner on Feb 3, 2023. It is now read-only.

Releases: liquibase/liquigraph

4.0.6 - Selda Bağcan

21 Feb 13:53
Compare
Choose a tag to compare

πŸ”Š This is the last planned release for Liquigraph 4.
Another release will follow for Liquigraph 3.

πŸ›‘ The Liquigraph project has reached End of Life and will not be maintained anymore πŸ‘‹.

πŸ€— Fear not though, the Neo4j plugin for Liquibase replaces Liquigraph. This release includes a migration utility from Liquigraph to Liquibase (see #447), available through the CLI and Maven plugin.

⚠️ This release also fixes security vulnerabilities, including one from the underlying JDBC driver which now defaults to the 4.0.5 version (see neo4j/neo4j-jdbc#291 for more information).

4.0.5 - πŸ”₯

21 Feb 13:21
Compare
Choose a tag to compare

πŸ™ˆ Move along, use 4.0.6 instead πŸ™ˆ

For the curious minds, the Maven plugin in 4.0.5 was not properly configured πŸ˜….

4.0.4 - Agnetha FΓ€ltskog

13 Sep 20:46
Compare
Choose a tag to compare

πŸ”ˆ Please note this is one of the last releases of Liquigraph, as its successor, the Neo4j plugin for Liquibase, is available. A migration path from Liquigraph to Liquibase is on its way.

The main change is the underlying JDBC driver version update to 4.0.4. This includes the following noteworth improvements:

  • support for neo4j+s, neo4j+ssc, bolt+s, bolt+ssc schemes (since the 4.0.2 and 4.0.3 releases of the JDBC driver actually)
  • fix for the Java driver which would prevent applications (such as the Liquigraph CLI) to complete if driver was not closed explicitly (see JDBC 4.0.4 above release notes)

Enjoy!

4.0.3 - Fatoumata Diawara

07 Jul 16:08
Compare
Choose a tag to compare

πŸ”ˆ Please note this is one of the last releases of Liquigraph, as its successor, the Neo4j plugin for Liquibase, is available. A migration path from Liquigraph to Liquibase is on its way.

Here are the noteworthy changes:

  • [#401] Introduce explicit dry-run and run commands to Liquigraph CLI.
    πŸ’₯ Breaking changes:
    - dry-run is now executed via liquigraph dry-run
    - run is now executed via liquigraph run
    - --help and --version are now exclusive and cannot be called on subcommands
  • [#418] Change JDBC driver dependency scope to runtime (thanks @AElMehdi)
  • [#434] Acquire fresh write connections instead of keeping a long-running ones. Thanks @DirkMahler!
    🧐 This will help users in dynamic cluster environments such as Neo4j Aura.

4.0.2 - Ennio Morricone

29 May 11:45
Compare
Choose a tag to compare

Apart from a few dependency bumps, here are the notable changes of this release:

  • [#386] Liquigraph now understands bolt+routing URLs, thanks @DirkMahler for the contribution πŸ™Œ
  • [#254] this is not a user-facing change, but we migrated Liquigraph to Testcontainers, significantly reducing the test complexity πŸ“¦

Another 4.x release will happen soon (just waiting for neo4j/neo4j-jdbc#228 to be released!).

Have fun with Liquigraph!

3.1.2 - Tiken Jah Fakoly

30 Apr 15:02
Compare
Choose a tag to compare

There has been a few internal improvements since 3.1.1 but also some externally-contributed user-facing features 🍾

  • πŸ€– Usage of Dependabot has been generalized to the whole repo, expect fresher/more secure deps! (Still a few corner cases to handle, but we're getting there!)
  • ⬇️ The minimum Neo4j JDBC driver has been decreased to 3.0.3 (not sure why I bumped it to 3.1 in the first place πŸ˜…)
  • πŸ”Œ [#241] Allow offline usage of Liquigraph - thanks @mattharr for this great contribution!

🍺 Note that the official Homebrew recipe has switched to 4.x versions.

This version will only be available via the custom tap, as soon as this issue is resolved (contributors welcome, πŸ˜‰ πŸ˜‰ ).

4.0.1 - Concha Buika

28 Apr 20:56
Compare
Choose a tag to compare

Let's try to release more often πŸ™
This one includes a cool improvement:

  • [#370] Add option to configure database instance name

This is relevant for users relying on the recently introduced multi-database support (works in Neo4j Desktop too!).
Big thanks to @maximus321 for not only requesting the feature but also implementing it! πŸ’ͺ

Note: master is now the branch for 4.x development, 3.x has been created for Liquigraph 3.x

4.0.0 - John Coltrane

02 Apr 14:09
Compare
Choose a tag to compare

And a wild Liquigraph 4.x release appears ✨

🧐 Changes since 3.1.1:

  • [c2dc5f6] Update Liquigraph to support Neo4j 4.x (includes JDK 11 baseline, Neo4j JDBC 4.x)
  • [#241] ("Back"port) Liquigraph will now work offline (thanks @mattharr) πŸš€
  • [54fc17f] Fix changeset retrieval order (seemed to work by coincidence until now πŸ€”)

2.0.3 - Manu Dibango

02 Apr 12:43
Compare
Choose a tag to compare

The 2.x deserves some ❀️ too!

  • [#241] (Backport) Liquigraph will now work offline (thanks @mattharr) πŸš€
  • [db8d06f] Fix changeset retrieval order (seemed to work by coincidence until now πŸ€” )

You should definitely upgrade to Liquigraph 3.x if you can (which requires a JDK 8 and Neo4j 3.x).
Some of Liquigraph 2.x dependencies cannot be upgraded anymore and are open to vulnerability issues. πŸ›

3.1.1 - Thomas Fersen

12 Mar 18:30
Compare
Choose a tag to compare

This is a loooong overdue release, apologies for the delay! πŸ˜…
By the way, if you or your company wants to support Liquigraph, please visit my Github Sponsors profile!

Here is the list of notable changes:

  • The project has now a code of conduct.
  • Do not include username and password in JDBC URI to work around neo4j/neo4j-jdbc#200
  • [#228] Fixing log level for postcondition execution
  • [#220] Remove lock in new connection if first attempt fails - this will make the locking cleanup mechanism much more resilient πŸ”’
  • We also got rid of Guava πŸ‘‹

Kudos to @oyvindwe for the contribution on Liquigraph and on the JDBC driver as well!
Thanks to Sebastien Latre for the logging fix!