v1.0.5

Fixed

• SQL files are no longer deleted before a down migration runs; if the down migration fails, the SQL file is kept since the migration is still applied.
• SQL files are now written to a temporary file and atomically renamed into place, so a process killed mid-migration can no longer leave a permanent, truncated SQL file behind.
• The migration SQL directory is now created with FileUtils.mkdir_p, eliminating a race condition between concurrent migration processes and supporting nested custom directories.
• Attaching the SQL subscriber is now thread safe, preventing duplicate subscribers (and duplicated SQL output) when migrations run in parallel threads.
• Ignored statement filters are now applied after stripping leading whitespace, so statements with leading whitespace no longer bypass them.
• The INSERT INTO schema_migrations statement written to SQL files now honors custom schema migrations table names and table name prefixes and suffixes.
• Connection labels from using_connection are no longer written to the SQL file when SQL logging is disabled.

Changed

• Rails 5.2 and Ruby 2.6 are the minimum supported versions.

Full Changelog: v1.0.4...v1.0.5

v1.0.4

What's Changed

• Delete sql file on failure by @bdurand in #6

Full Changelog: v1.0.3...v1.0.4

v1.0.3

What's Changed

• Don't update already existing schema files by @bdurand in #4

Full Changelog: v1.0.2...v1.0.3