Skip to content

Releases: graphile/migrate

v0.0.11

09 Sep 17:57
Compare
Choose a tag to compare

We now use chokidar's awaitWriteFinish due to a race condition in watch mode when you write current.sql and graphile-migrate notices the write before it's complete. This change introduces about 200ms of latency to watch mode, but increases stability.

v0.0.10

09 Sep 17:58
Compare
Choose a tag to compare

Add Windows note to README, fix an error message bug.

v0.0.9

23 Aug 10:21
Compare
Choose a tag to compare

Add GM_DBUSER envvar, thanks to @alaister

v0.0.8

23 Aug 09:12
Compare
Choose a tag to compare

Command actions now have access to the full environment (we may put this behind an opt-in flag at a later time), and also receive the GM_DBNAME envvar. The main reason for this is to allow a script that runs as the PG superuser to install certain privileged extensions.

v0.0.7

20 Aug 17:48
Compare
Choose a tag to compare

Fixes a bug where graphile-migrate watch --once --shadow ran current.sql against the normal DB rather than the shadow DB.

v0.0.6

20 Aug 12:56
Compare
Choose a tag to compare

Added afterCurrent action.

Refactored commands into their own files.

Added a number of tests.

Actions can be configured to only run on the shadow DB.

A few fixes.

v0.0.5

19 Aug 14:16
Compare
Choose a tag to compare

Added afterAllMigrations action, useful for dumping the schema after migrations complete:

  "afterAllMigrations": [{ "command": "pg_dump --schema-only --no-owner --exclude-schema=graphile_migrate --exclude-schema=graphile_worker --file=data/schema.sql \"$GM_DBURL\"" }]

Updated the README.

Changed the envvars available to "action" commands (see README).

Updated a number of dependencies.

(v0.0.4 was never released)

v0.0.3

19 Jun 19:36
Compare
Choose a tag to compare
  • Fix issue where order of placeholders matters
  • Add graphile-migrate status command