sobolevn

Yeah, I also consider `django-migration-linter` as `django-incompatible-migration-linter` 🙂

@xi can you please think of any simple test cases to reproduce this? 🤔

Should we always call this function on our side? What do you think? 🤔

Then, PR is welcome. Let's test it!

My idea is that: - We should issue `WARNING` messages when there's something not quite right with the app (we found any kind of rule violations) - We should issue...

Related: https://github.com/wemake-services/django-test-migrations/pull/91/files/a7f72b086d3f0076418674febc745d4626fdb5b5..4b6eeb44aa23441d3179ad3bcce76a4845078afa#r457584209

We had a `0.3.0` release on git: https://github.com/wemake-services/caddy-gen/releases/tag/0.3.0 For some reason `Dockerhub` ignored it.

@Siemko any ideas how we can fix the CI? https://travis-ci.com/github/wemake-services/caddy-gen/builds/176069791

The thing is: we don't what to release `1.5.0` while we have our CI broken. Can you please help fixing it?

Yes, `0.4.0` 🙂 Here's what's wrong: https://travis-ci.com/github/wemake-services/caddy-gen