3.1.0

• New: Implement ReleaseNotes as TemplateFolder
• New: Add ability to have custom passwords for db/schemas to connect as schema owner
• New: Force release.sh to merge with stratie to theirs
• New: Only add version tag, when not exits
• Fix: many typos
• New: Add current as option to version in release.sh
• Upd: refresh tutorial to reflect current chan

Release 3.0.0

• New: When using release.sh you can set version to: major, minor or patch. dbFlow will calcualte the right version number for you
• New: During deployment, translated Applications are se offline too.
• New: Logs will be written to a new Environment var: LOG_PATH. From now on, the depot is not responsible for storing log data. So, when using LOG_PATH inside instance directories, logs should be written to ./${LOG_PATH}. And here (instance directory) it is ok to commit the files as well. This will keep a nice install log history.
• Fix: Setting Applications online occurs only to untouched Applications.
• New: When creating deployments and depot path is a git directory as well, the actual artefact is pushed to the remote too. So you can have a Jenkins or something like that listening to pushed on your depot repository.
• New: The version will be a tag in the target branch and will the tag will be moved to the master/main branch as well.
• New: The jobs folder will be executed after the dml folder and it's childs. So, you can consume data in the job files you have used in dml scripts before.
• New: The version of bash is written to the output.
• New: When a table file is marked as new in the target branch by git, it is executed allthough there could be table_ddl files, which alters the same table. This is new and in important change. So when releasing often to a test or uat branch and later just to a master/main branch, then new tables will be created by running just the create-table-script. Not the 10 changes which were created and deployed during the last sprints. See documentation for more infos.
• New: You have an option to use the old behavior (--forceddl)
• New: Now object-hooks will always be executed. Weather there were objects in the specific file or not.
• New: Environment Var: REMIND_ME When this var is set, it will be prompted, when building a deployment, just for you to remind you on something specific.
• Fix: Many small improvements

2.4.0

What's Changed

• New: Add flag -a/--apply to build.sh
• New: Old flag -a/--shipall is renamed to -t/--transferall
• Fix: Missing privileges on sh files after copyto target
• Fix: Logpath is added to .gitignore
• Some fixes

Full Changelog: 2.3.0...2.4.0

2.3.1 - Albatross

Fix Mac encoding of base64 changelog (#21)

2.3.0

What has changed

• New: Create readme.md when generating project
• New: apply.sh can now run a stepwise installation using flag --stepwise
• New: setup.sh --apply will only generate apply.env file
• New: added new env var LOG_PATH which defines an additional path to write the logs to
• New: packages or types are grouped by Specifications, Bodies, SQL-Files
• New: Install APEX Apps to ID of folder, not to original
• Fix: Synonyms will be dropped in init mode as well
• Fix: Gen Changelog on Mac

2.1.0

• Some fixes
• Schema-Hooks with suffic ".table.sql" are now called for each touched table

2.0.0

New Release with new parameter parsing!
You have to change your scripts. Please see <setup|build|apply|releas>.sh --help for further informations.

1.0.1

v1.0.0

Merge branch 'develop'

1.0.0

Starting with ghpages and mkdocs

0.9.beta

What's Changed

• Korrektur drop_all.sql für materialized views by @Asgarmagol in #7
• Erweiterung drop_all.sql (#7) by @MaikMichel in #8

New Contributors

• @Asgarmagol made their first contribution in #7

Full Changelog: 0.8.beta...0.9.beta