95 lines
3.0 KiB
Markdown
95 lines
3.0 KiB
Markdown
## 1.0.0
|
|
|
|
*Breaking changes* of the linter usage. The linter now is a Django management command.
|
|
It shoud be used with a `python manage.py lintmigrations` followed by the usual options.
|
|
Additionally, the linter now needs to be added the to the `INSTALLED_APPS` in your Django settings.
|
|
|
|
* The linter is now much faster: we don't setup django once for each migration
|
|
* The linter is now more robust: we rely on Django internals to discover migrations
|
|
* Clean up of the testing setup: it is cleaner, less brittle and we have more confidence that it works
|
|
|
|
## 0.1.5
|
|
|
|
* Bug fix: handle migration files with spaces in their name by quoting the migration name
|
|
|
|
## 0.1.4
|
|
|
|
* Explicitly test for mysql, sqlite3 and postgresql
|
|
* Fix alter column type detection in postgresql
|
|
* Do not create cache folder when -no-cache option
|
|
* Fix tests on Windows
|
|
* Use the same Python interpreter as used for launching the linter, instead of manually trying to re-create the path
|
|
|
|
## 0.1.3
|
|
|
|
* Fixes migrations that are ignored to generate empty SQL, that PostgreSQL complains about. It throws an exception making migrations fail, that are in fact valid. (Thanks to @fevral13 and @mes3yd)
|
|
* Add options -V and --version to show the current linter version
|
|
|
|
## 0.1.2
|
|
|
|
* Bug fix: handle when the linter is called in the working dir django-migration-linter .
|
|
* Bug fix: don't assume that the git root is at the same path as the django project
|
|
|
|
## 0.1.1
|
|
|
|
* Fix caching when app is in a folder and not at the root of the project
|
|
* Do not check for .git folder at root, because it might be located somewhere else. Let git itself do the job
|
|
* Make some imports relative
|
|
|
|
## 0.1.0
|
|
|
|
The django migration linter is now set to a Beta version, instead of Alpha since it has been used for quite some time.
|
|
|
|
Version 0.1.0 comes with:
|
|
|
|
* Possibility to ignore migration files entirely (without specifying them on the command line)
|
|
* This can be used by adding the migration operation IgnoreMigration() in the migrations operations list. See readme
|
|
* Caching. We cache failed and succeeded migrations (w.r.t. migration linting) in a cache file.
|
|
* Each migration file is stored as the MD5 hash of its content with the result of the linting
|
|
|
|
Other things:
|
|
|
|
* Added support for Python 3.7
|
|
* Added support for Django 2.1
|
|
* The codebase is now in black format to improve Python-code readability
|
|
* 2019 ! Happy new year
|
|
|
|
## 0.0.7
|
|
|
|
* Minor bug fix when no errors detected
|
|
|
|
## 0.0.6
|
|
|
|
* Use logger correctly
|
|
* Drop django 1.10 support
|
|
|
|
## 0.0.5
|
|
|
|
* Only consider added migrations during linting
|
|
* Change readme to rst format (for PyPi)
|
|
* Added examples folder
|
|
* Add django (at least 1.10) as requirement for the linter
|
|
|
|
## 0.0.4
|
|
|
|
Assure compatibility for multiple python and django versions.
|
|
|
|
* Try to improve PyPi readme
|
|
* Better error messages
|
|
|
|
## 0.0.3
|
|
|
|
* Made a mistake and accidentally deleted 0.0.2 from PyPi
|
|
|
|
## 0.0.2
|
|
|
|
* Python 3 compatibility
|
|
* Faster migration gathering
|
|
|
|
* Code base refactoring
|
|
* Test base refactoring
|
|
|
|
## 0.0.1
|
|
|
|
First version of command line tool to lint django migrations.
|