All notable changes to this project will be documented in this file. See standard-version for commit guidelines.
3.2.6 (2019-03-20)
- 🐛 Fixed
knex-migrator migrate --init
3.2.1 (2019-03-20)
- 🐛 Fixed option collision with commander (
--version
vs--v
)
3.2.0 (2019-03-20)
✨ Added ability to rollback to a specific version
3.1.6 (2018-04-30)
- 🔥Drop Node v4 support
- 🐛Fixed incorrect version number comparison
- 🐛Fixed wrong folders order on db initialisation
- 🐛Fixed comparing expected and actual migration tasks
3.1.3 (2018-01-02)
- Optimised error message for lock
- Added support for specifying the config via options
3.1.2 (2017-12-05)
- Make database upgrades more relaxed
3.1.1 (2017-12-05)
- Added protection against database migrations
3.1.0 (2017-12-05)
- Added more database upgrades
- Added unique constaint to the migrations table
- Define field lengths for migrations table
3.0.10 (2017-12-04)
- Fixed
acquired_at
andreleased_at
with correct date format
3.0.9 (2017-12-04)
- Do not unlock if lock was never acquired
3.0.8 (2017-12-04)
- Added more npm keywords
- Rollback should not happen if lock was never acquired
3.0.7 (2017-11-15)
- Added missing
--force
flag forknex-migrator reset
3.0.6 (2017-11-04)
- Do not throw error on reset, otherwise it's harder to handle this via the JS API
- There is no good reason to throw an error, so revert to success response
3.0.5 (2017-11-04)
- Fixed order of rollback
3.0.4 (2017-11-04)
- Fixed rollback for init scripts
3.0.3 (2017-11-04)
- Fixed
--force
flag forknex-migrator rollback
3.0.2 (2017-11-03)
- Fixed missing throw/catch behaviour,
3.0.1 (2017-11-03)
- Fixed binary for
knex-migrator rollback
3.0.0 (2017-11-03)
- You have to export
up
anddown
in your migration scripts.down
is optional, but highly recommended, otherwise on failure your changes won't rollback completely. - The
options
object which is passed into the migration script contains now by default a connection object. (options.connection
). You have to explicit enable transactions, see README. - A new migrations lock table get's added as soon as you run any command. You don't have to worry about that.
- Expect bug fixes in the upcoming days.
- Support full rollback (auto rollback on error)
- Shutdown hook
- Concurrency and locking
- A new shiny
rollback
command for manual rollback if needed.
2.1.9 (2017-10-26)
- Enabled Node 8 Support
2.1.9 (2017-10-24)
- Fixed migration order on db initialisation