drm-cli v1.1.0 Release Notes #5
dband-drm
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
What's New
v1.1.0 is the biggest update since the initial release. We've expanded database support, added two new migration tool integrations, and shipped several reliability and usability improvements that came directly from feedback on v1.0.
Here's what's in this release.
New Database Support
PostgreSQL
drm-cli now supports PostgreSQL deployments out of the box. Use it with Liquibase or Flyway — drm-cli layers on top of whichever tool you're already using, adding release history tracking, encrypted credentials, automated retries, and pre/post deployment scripts.
Oracle
Oracle deployments are now fully supported via Liquibase and Flyway. No Oracle Enterprise license required for the release management layer — drm-cli is free and open-source, and that doesn't change based on which database you're targeting.
New Migration Tool Support
Liquibase
Liquibase is now a first-class supported migration tool in drm-cli. If you're running Liquibase changelogs today, drm-cli can wrap your existing workflow without requiring changes to your changelog structure.
Flyway
Flyway is now fully supported alongside SSDT. Point drm-cli at your existing Flyway migration directory and it will handle the release orchestration layer on top.
Supported Matrix (v1.1.0)
Pre/Post Deployment Scripts
v1.1.0 introduces support for pre-deployment and post-deployment scripts — SQL or shell scripts that run before or after every deployment, regardless of which solutions are included in the release.
This is useful for:
Configuration is handled in your release definition file. See the pre/post scripts documentation for full details.
Release History Tracking
Release history tracking introduced in v1.0 continues to work unchanged in v1.1.0 and now covers PostgreSQL and Oracle deployments in addition to SQL Server. Every deployment — regardless of database or migration tool — is written to your release history store with a full audit record: what ran, when, against which target, and whether it succeeded.
Encrypted Credentials
Connection string encryption introduced in v1.0 is now supported for PostgreSQL and Oracle targets. Credentials for all supported databases can be encrypted at rest using the same encryption workflow.
Automated Retries
Retry logic now applies to PostgreSQL and Oracle deployments. If a connection or deployment step fails transiently, drm-cli will retry according to your configured retry policy before surfacing a failure. This behaviour was previously available for SQL Server only.
Breaking Changes
There are no breaking changes in this release. v1.0 release definition files are valid in v1.1.0 without modification.
If you are upgrading from v1.0, see the upgrade guide for the recommended steps. The short version: swap the binary, run
drm-cli --versionto confirm, and continue. Your existing release history and configuration are preserved.Bug Fixes
Installation
Or download the binary directly from the releases page.
Documentation
Full documentation for v1.1.0 is available at docs.drm-cli.com.
Feedback
If you hit an issue, open a GitHub issue. If you have a question or want to discuss a use case, open a Discussion.
We read everything.
What's Next
v1.2 is in planning. Early targets include MySQL support, BigQuery, and scheduled deployments. Watch this repo or follow d-band on GitHub to stay up to date.
Full changelog: v1.0.0...v1.1.0
Beta Was this translation helpful? Give feedback.
All reactions