Not all the breaking changes we’ve made are strictly related to ` check` feature, but it will only be available in Version 9, and to use it you may need to be aware of some things. ` -codeStandards`: coming later in the year, code standards is both a quality check on the script being written as well as a compliance check on the SQL that’s being executed.` -drift`: the ability to check whether the deployment target is in the state you expect it to be in prior to a migration, not to mention understanding what’s changed if it has drifted.` -changes` : the ability to get a comprehensive report of the changes to the target database your pending migrations will affect.“Check” is a new verb, under which we’ll wrap several capabilities including: The headline feature for Version 9 is ` check`. In the coming weeks we’ll be releasing Version 9 to General Availability (GA).Ī major version change is both an opportunity to introduce a new feature, as well as an opportunity to keep Flyway up to date and make retrospective improvements. A patch version when you make backwards compatible bug fixes.Įvery year for the past 5 years we’ve made a conscious effort to introduce a major new version of Flyway, and this year is no different.A minor version when you add functionality in a backwards compatible manner, and.A major version when you make incompatible API changes,.Not a subscriber? Sign up now Flyway uses semantic versioningįlyway follows a semantic approach to version numbering which, following the convention described by means: Newsletter subscribers always get the heads-up first. Here’s everything you need to stay ahead. Upgrading to 9 will introduce new capabilities like the `check` command, but it also brings API changes that you may need to account for. Version 9 of Flyway brings new features, capabilities, and many small improvements. Version 9 is coming: what developers need to know
0 kommentar(er)
