Django-celery-beat: Release version 1.1.1

[thedrow]

We need to ensure that this time there's a changelog for all previous releases as well.
@auvipy Would you mind taking care of this release?

[muhtarc4n]

Do we have any ETA?

[sobolevn]

Yeap, that's breaking our release process. Since we do this check in our CI: python manage.py makemigrations --dry-run --check: https://github.com/wemake-services/wemake-django-template/blob/master/%7B%7Bcookiecutter.project_name%7D%7D/docker/django/gunicorn.sh#L26

[thedrow]

ping @auvipy

[muhtarc4n]

Guys, are we going to release bug fix?

[muhtarc4n]

@sobolevn We do dry-run in PR checks. It helps us to catch migration conflicts but right now we are blocked in django upgrade branch due to bug.

[ShaheedHaque]

I realise that getting a release out can be fraught, but it would be wonderful if #122 might be snuck in to 1.1.1. I believe it is a 1-line fix (famous last words...).

[ShaheedHaque]

So of course it was not 1-line, but PR #123 addresses issue #122.

[muhtarc4n]

Are we going to release this bug fix version?

[thedrow]

1.1.1 released. Thank you for your patience.