chore(release): version packages
This commit is contained in:
parent
f8a5cc728d
commit
ff89dd4f86
31 changed files with 93 additions and 76 deletions
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@emigrate/cli': patch
|
||||
---
|
||||
|
||||
Only include files when collecting migrations, i.e. it should be possible to have folders inside your migrations folder.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@emigrate/types': minor
|
||||
---
|
||||
|
||||
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.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@emigrate/cli': minor
|
||||
---
|
||||
|
||||
Add support for passing the relative path to a migration file to remove from the history using the "remove" command
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@emigrate/cli': minor
|
||||
---
|
||||
|
||||
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.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@emigrate/cli': patch
|
||||
---
|
||||
|
||||
Don't dim decimal points in durations in the default reporter
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@emigrate/docs': minor
|
||||
---
|
||||
|
||||
Document the changes to the "remove" command, specifically that it also accepts relative file paths now
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@emigrate/cli': patch
|
||||
---
|
||||
|
||||
Set Emigrate error instance names from their respective constructor's name for consistency and correct error deserialization.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@emigrate/reporter-pino': minor
|
||||
---
|
||||
|
||||
Adapt to the new Reporter interface, i.e. the removal of the "remove" command related methods
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
---
|
||||
'@emigrate/postgres': patch
|
||||
'@emigrate/mysql': patch
|
||||
---
|
||||
|
||||
Make sure the storage initialization crashes when a database connection can't be established
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
---
|
||||
'@emigrate/reporter-pino': patch
|
||||
'@emigrate/cli': patch
|
||||
---
|
||||
|
||||
Show number of skipped migrations correctly in the command output
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@emigrate/cli': minor
|
||||
---
|
||||
|
||||
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.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@emigrate/docs': minor
|
||||
---
|
||||
|
||||
Document the changes to the "up" command's `--from` and `--to` options, specifically that they can take relative file paths and that the given migration must exist.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
'@emigrate/cli': minor
|
||||
---
|
||||
|
||||
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.
|
||||
Loading…
Add table
Add a link
Reference in a new issue