STDERR output from liquibase command should be EMPTY when NO ERRORS!

When I run a SUCCESSFUL liquibase command (with NO ERRORS), with my STDOUT piped to a STDOUT text-file, and STDERR piped to a STDERR text-file, the STDERR file should be EMPTY. Instead, it contains the liquibase header and success information, which should only appear in the STDOUT file. Note that this header and success info does NOT appear in the STDOUT file, but it should! The STDERR file should ONLY contain ERRORS – possibly WITH header info, but not JUST with header info!!! This is real BASIC computer programming best-practices folks!!!

When I run liquibase WITH ERRORS, the header and Error info appears in the STDERR text-file, which it should, and the STDOUT file is EMPTY (although it should probably ALSO contain the Header and Error info!).

I’m running liquibase 4.32.0 on a RHEL8 Linux VM. Here’s the contents of my STDERR text-file from a SUCCESSFUL run with NO ERRORS…

cat example-mysql-changelog.sql.stderr.txt
####################################################

_ _ _ _

| | () () |

| | _ __ _ _ _ | |_ __ _ ___ ___

| | | |/ _ | | | | | '_ \ / _ / __|/ _ \

| || | (| | || | | |) | (| _ \ __/

_/|_, |_,||./ _,|/__|

| |

|_|

Get documentation at docs.liquibase.com

Get certified courses at learn.liquibase.com

####################################################
Starting Liquibase at 18:01:00 using Java 17.0.15 (version 4.32.0 #8159 built at 2025-05-19 23:00+0000)
Liquibase Version: 4.32.0
Liquibase Open Source 4.32.0 by Liquibase
Logs saved to example-mysql-changelog.sql.log.txt
Liquibase command ‘update-sql’ was executed successfully.

Please submit this to Liquibase Development to FIX ASAP! Thanks!!

Thanks for talking the time to write this up @ekalwa. The appropriate channel for Liquibase issues is our GitHub repo. Please submit your findings there and our dev team will review it.