@emigrate/reporter-pino@0.6.3

Patch Changes

• 081ab34: Make sure Pino outputs logs in Bun environments

@emigrate/cli@0.18.2

Patch Changes

• 4152209: Handle the case where the config is returned as an object with a nested default property

@emigrate/cli@0.18.1

Patch Changes

• 57a0991: Cleanup AbortSignal listeners when they are not needed to avoid MaxListenersExceededWarning when migrating many migrations at once

@emigrate/reporter-pino@0.6.2

Patch Changes

• 1065322: Show correct status for migrations for the "list" and "new" commands

@emigrate/mysql@0.2.8

Patch Changes

• 17feb2d: Only unreference connections in a Bun environment as it crashes Node for some reason, without even throwing an error that is

@emigrate/mysql@0.2.7

Patch Changes

• 198aa54: Unreference all connections automatically so that they don't hinder the process from exiting. This is especially needed in Bun environments as it seems to handle sockets differently regarding this matter than NodeJS.

@emigrate/cli@0.18.0

Minor Changes

• c838ffb: Make it possible to write the Emigrate configuration file in TypeScript and load it using tsx in a NodeJS environment by importing packages provided using the --import CLI option before loading the configuration file. This makes it possible to run Emigrate in production with a configuration file written in TypeScript without having the typescript package installed.
• 18382ce: Add a built-in "json" reporter for outputting a single JSON object
• 18382ce: Rename the "default" reporter to "pretty" and make it possible to specify it using the --reporter CLI option or in the configuration file

Patch Changes

• c838ffb: Don't use the typescript package for loading an Emigrate configuration file written in TypeScript in a Bun or Deno environment

@emigrate/types@0.12.1

Patch Changes

• db656c2: Enable NPM provenance

@emigrate/types@0.12.0

Minor Changes

• 94ad9fe: Remove the "remove" command specific reporter methods. So instead of using onMigrationRemoveStart, onMigrationRemoveSuccess and onMigrationRemoveError the onMigrationStart, onMigrationSuccess and onMigrationError methods should be used and the reporter can still format the output differently depending on the current command (which it receives in the onInit method). This is a BREAKING CHANGE.

@emigrate/tsconfig@1.0.2

Patch Changes

• db656c2: Enable NPM provenance