Migrations
This version didn't actually add new migrations (but existing migrations were renamed)
A consequence of this, if you're using Django Migrations and ran migrations pre-0.17 is that one of the Django migrations was renamed, which confuses Django. Before running the Migrations for 0.17.0, you're invited to run the following Django code in the Django shell (manage.py shell
):
>>> from django.db.migrations.recorder import MigrationRecorder
>>> MigrationRecorder.Migration.objects.filter(app="procrastinate", name="0001_baseline").update(name="0001_initial")
Starting at this release, migrations can be run while the system runs, provided certain conditions are met.
See the migrations doc for more information.
Work on migrations:
- Use underscores in migration script names (#345)
- Document new rules for database migrations (#342)
- Rename SQL migrations (#347)
- Rename migration: wrong index number (#350)
- Django migrations: generate on the fly via import hooks (#340)
Breaking Changes
- Django migrations, see above.
procrastinate healthchecks
now doesn't report the number of jobs anymore. Useprocrastinate shell
for that.
Miscellaneous
- Adjust badges (#337)
- Rename Job Store > Job Manager (#335)
- Report test workflow success in Check API (#322)
- Don't test the PRs, just test the branches (#348)
- Ignore aiopg warnings that we can't do anything about (#338)
- Remove HealthCheckRunner, simplify healthchecks (#339)