1.3.0

It looks like the CI doesn't like $blueprint->dropCulmn.
We thus have to remove it from the migrations and instead
remove the column we were dropping froml its original migration.
This isn't a problem since production has already been migrated.

1.2.0

1.1.1

This is needed because storage is declared as a volume in the
docker-compose file. We thus cannon use the api documentation provided
in the container.

1.1.0