@emigrate/[email protected]

Patch Changes

• Updated dependencies [94ad9fe]
  • @emigrate/[email protected]
  • @emigrate/[email protected]

@emigrate/[email protected]

Patch Changes

• db656c2: Enable NPM provenance
• Updated dependencies [db656c2]
  • @emigrate/[email protected]
  • @emigrate/[email protected]

@emigrate/[email protected]

Patch Changes

• f8a5cc7: Make sure the storage initialization crashes when a database connection can't be established
• Updated dependencies [94ad9fe]
  • @emigrate/[email protected]
  • @emigrate/[email protected]

@emigrate/[email protected]

Patch Changes

• 61cbcbd: Force exiting after 10 seconds should not change the exit code, i.e. if all migrations have run successfully the exit code should be 0

@emigrate/[email protected]

Patch Changes

• 543b7f6: Use setTimeout/setInterval from "node:timers" so that .unref() correctly works with Bun
• db656c2: Enable NPM provenance
• Updated dependencies [db656c2]
  • @emigrate/[email protected]
  • @emigrate/[email protected]

@emigrate/[email protected]

Minor Changes

• 0faebbe: Add support for passing the relative path to a migration file to remove from the history using the "remove" command
• 9109238: When the --from or --to CLI options are used the given migration name (or path to migration file) must exist. This is a BREAKING CHANGE from before. The reasoning is that by forcing the migrations to exist you avoid accidentally running migrations you don't intend to, because a simple typo could have the effect that many unwanted migrations is executed so it's better to show an error if that's the case.
• 1f139fd: Completely rework how the "remove" command is run, this is to make it more similar to the "up" and "list" command as now it will also use the onMigrationStart, onMigrationSuccess and onMigrationError reporter methods when reporting the command progress. It's also in preparation for adding --from and --to CLI options for the "remove" command, similar to how the same options work for the "up" command.
• 9109238: Add support for passing relative paths to migration files as the --from and --to CLI options. This is very useful from terminals that support autocomplete for file paths. It also makes it possible to copy the path to a migration file from Emigrate's output and use that as either --from and --to directly.

Patch Changes

• f1b9098: Only include files when collecting migrations, i.e. it should be possible to have folders inside your migrations folder.
• 2f6b4d2: Don't dim decimal points in durations in the default reporter
• f2d4bb3: Set Emigrate error instance names from their respective constructor's name for consistency and correct error deserialization.
• ef45be9: Show number of skipped migrations correctly in the command output
• Updated dependencies [94ad9fe]
  • @emigrate/[email protected]
  • @emigrate/[email protected]

@emigrate/[email protected]

Patch Changes

• b56b6da: Handle migration history entries without file extensions for migration files with periods in their names that are not part of the file extension. Previously Emigrate would attempt to re-run these migrations, but now it will correctly ignore them. E.g. the migration history contains an entry for "migration.file.name" and the migration file is named "migration.file.name.js" it will not be re-run.

@emigrate/[email protected]

Minor Changes

• ce15648: Add type for onAbort Reporter method

@emigrate/[email protected]

Patch Changes

• Updated dependencies [ce15648]
  • @emigrate/[email protected]

@emigrate/[email protected]

Minor Changes

• a4da353: Handle the new onAbort method

Patch Changes

• Updated dependencies [ce15648]
  • @emigrate/[email protected]