This release just disables SQLite foreign keys, since some people already have invalid rows in the database, which caused issues when SQLite re-checked the rows during database migrations (#360). The invalid rows shouldn't cause any actual issues, since the bridge uses foreign keys primarily for cascade delete purposes.
If you're using Postgres, this update is not necessary.