Skip to content

v4.3.0
Compare
Choose a tag to compare
@tchapi tchapi released this 21 Nov 12:10
v4.3.0
a045d80

What's Changed

  • Fix a regression introduced in 4.2.0 about the OPTIONS call (#124)

💁🏼‍♂️ If you're coming from a release before 4.2.0, please do not forget to run the migration process below

How to migrate your database

Warning

While not exactly breaking, you have to update the database schema to have the correct column type. Follow the instructions below.

0. Back up your database

This is a safety precaution in case you end up messing with a migration or the database in general. It's highly recommended, even if you know exactly what you're doing.

1. Update the code and migrate

You can now update the code (either directly or get the up to date container), and then run the remaining migrations with:

bin/console doctrine:migrations:migrate

Note

Some migrations are for PostgreSQL, some for MySQL, so it's perfectly normal if you always have a "New" migration that is skipped, and if you're not at the latest one.

Full Changelog: v4.2.1...v4.3.0

Assets 2
Loading