Changed - Project is now configured with setup.cfg. There should be no change to package users.
3.3.0
Not secure
Added - Added processing of schemachange-config.yml with jinja templating engine. - Included new Jinja function env_var for accessing environmental variables from the config file.
3.2.2
Not secure
Added - Restored CLI tests, hopefully less fragile now. - Added Github CI workflow to run unit tests and a basic execution test. - `schemachange.cli.main` is now defined as `def main(argv: List[str]=sys.argv)`, to allow consumers to pass a list of arguments easily.
3.2.1
Not secure
Fixed - Jinja Template Engine was not recognising scripts in subfolders on windows machines. Jinja was expecting the paths to follow a unix style ie SQL/V2.0.0__ADHOC_SCRIPT.sql but on windows machines this was being passed through as SQL\V2.0.0__ADHOC_SCRIPT.sql.
Removed - Removed fragile unit tests in test_main.py.
3.2.0
Not secure
Added - Added support for jinja templates. Any file ending .sql or .sql.jinja will be processed using the [Jinja engine](https://jinja.palletsprojects.com/) - Added a new optional parameter `--modules-folder` to specify where common jinja template, macro or include files reside - Added new subcommands render and deploy - The render command can be used to display the final script to the command line. - The existing functionality moved to a new deploy subcommand - Fall back behaviour to assume deploy sub command if none provided - Added reserved variable name `schemachange` and an error will now be raised if supplied by the user via --vars
Changed - Added check for duplicate filenames. An error will now be generated should two scripts in different folders have the same name. The old behaviour resulted in just the last found script being included for execution.
3.1.1
Changed - Loosen dependency version constraints - Fix crash on dry run with no change history table