chore(release): version packages

.changeset/cuddly-peaches-look.md

@@ -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.

.changeset/eleven-files-love.md

@@ -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.

.changeset/odd-foxes-mix.md

@@ -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

.changeset/plenty-insects-accept.md

@@ -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.

.changeset/purple-eagles-speak.md

@@ -1,5 +0,0 @@
----
-'@emigrate/cli': patch
----
-
-Don't dim decimal points in durations in the default reporter

.changeset/rude-eels-tap.md

@@ -1,5 +0,0 @@
----
-'@emigrate/docs': minor
----
-
-Document the changes to the "remove" command, specifically that it also accepts relative file paths now

.changeset/sharp-cows-joke.md

@@ -1,5 +0,0 @@
----
-'@emigrate/cli': patch
----
-
-Set Emigrate error instance names from their respective constructor's name for consistency and correct error deserialization.

.changeset/tame-apples-lick.md

@@ -1,5 +0,0 @@
----
-'@emigrate/reporter-pino': minor
----
-
-Adapt to the new Reporter interface, i.e. the removal of the "remove" command related methods

.changeset/tasty-bulldogs-guess.md

@@ -1,6 +0,0 @@
----
-'@emigrate/postgres': patch
-'@emigrate/mysql': patch
----
-
-Make sure the storage initialization crashes when a database connection can't be established

.changeset/thick-days-look.md

@@ -1,6 +0,0 @@
----
-'@emigrate/reporter-pino': patch
-'@emigrate/cli': patch
----
-
-Show number of skipped migrations correctly in the command output

.changeset/thin-pillows-obey.md

@@ -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.

.changeset/tricky-turkeys-refuse.md

@@ -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.

.changeset/twelve-hairs-relate.md

@@ -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.

docs/CHANGELOG.md

@@ -1,5 +1,12 @@
 # @emigrate/docs
 
+## 0.3.0
+
+### Minor Changes
+
+- f6761fe: Document the changes to the "remove" command, specifically that it also accepts relative file paths now
+- 9109238: 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.
+
 ## 0.2.0
 
 ### Minor Changes

docs/package.json

@@ -2,7 +2,7 @@
   "name": "@emigrate/docs",
   "private": true,
   "type": "module",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "scripts": {
     "dev": "astro dev",
     "start": "astro dev",

packages/cli/CHANGELOG.md

@@ -1,5 +1,24 @@
 # @emigrate/cli
 
+## 0.17.0
+
+### 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/types@0.12.0
+  - @emigrate/plugin-tools@0.9.5
+
 ## 0.16.2
 
 ### Patch Changes

packages/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@emigrate/cli",
-  "version": "0.16.2",
+  "version": "0.17.0",
   "publishConfig": {
     "access": "public"
   },

packages/mysql/CHANGELOG.md

@@ -1,5 +1,14 @@
 # @emigrate/mysql
 
+## 0.2.5
+
+### Patch Changes
+
+- f8a5cc7: Make sure the storage initialization crashes when a database connection can't be established
+- Updated dependencies [94ad9fe]
+  - @emigrate/types@0.12.0
+  - @emigrate/plugin-tools@0.9.5
+
 ## 0.2.4
 
 ### Patch Changes

packages/mysql/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@emigrate/mysql",
-  "version": "0.2.4",
+  "version": "0.2.5",
   "publishConfig": {
     "access": "public"
   },

packages/plugin-generate-js/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @emigrate/plugin-generate-js
 
+## 0.3.5
+
+### Patch Changes
+
+- Updated dependencies [94ad9fe]
+  - @emigrate/types@0.12.0
+  - @emigrate/plugin-tools@0.9.5
+
 ## 0.3.4
 
 ### Patch Changes

packages/plugin-generate-js/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@emigrate/plugin-generate-js",
-  "version": "0.3.4",
+  "version": "0.3.5",
   "publishConfig": {
     "access": "public"
   },

packages/plugin-tools/CHANGELOG.md

@@ -1,5 +1,12 @@
 # @emigrate/plugin-tools
 
+## 0.9.5
+
+### Patch Changes
+
+- Updated dependencies [94ad9fe]
+  - @emigrate/types@0.12.0
+
 ## 0.9.4
 
 ### Patch Changes

packages/plugin-tools/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@emigrate/plugin-tools",
-  "version": "0.9.4",
+  "version": "0.9.5",
   "publishConfig": {
     "access": "public"
   },

packages/postgres/CHANGELOG.md

@@ -1,5 +1,14 @@
 # @emigrate/postgres
 
+## 0.2.5
+
+### Patch Changes
+
+- f8a5cc7: Make sure the storage initialization crashes when a database connection can't be established
+- Updated dependencies [94ad9fe]
+  - @emigrate/types@0.12.0
+  - @emigrate/plugin-tools@0.9.5
+
 ## 0.2.4
 
 ### Patch Changes

packages/postgres/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@emigrate/postgres",
-  "version": "0.2.4",
+  "version": "0.2.5",
   "publishConfig": {
     "access": "public"
   },

packages/reporter-pino/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @emigrate/reporter-pino
 
+## 0.6.0
+
+### Minor Changes
+
+- 86e0d52: Adapt to the new Reporter interface, i.e. the removal of the "remove" command related methods
+
+### Patch Changes
+
+- ef45be9: Show number of skipped migrations correctly in the command output
+- Updated dependencies [94ad9fe]
+  - @emigrate/types@0.12.0
+
 ## 0.5.0
 
 ### Minor Changes

packages/reporter-pino/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@emigrate/reporter-pino",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "publishConfig": {
     "access": "public"
   },

packages/storage-fs/CHANGELOG.md

@@ -1,5 +1,12 @@
 # @emigrate/storage-fs
 
+## 0.4.5
+
+### Patch Changes
+
+- Updated dependencies [94ad9fe]
+  - @emigrate/types@0.12.0
+
 ## 0.4.4
 
 ### Patch Changes

packages/storage-fs/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@emigrate/storage-fs",
-  "version": "0.4.4",
+  "version": "0.4.5",
   "publishConfig": {
     "access": "public"
   },

packages/types/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @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.
+
 ## 0.11.0
 
 ### Minor Changes

packages/types/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@emigrate/types",
-  "version": "0.11.0",
+  "version": "0.12.0",
   "publishConfig": {
     "access": "public"
   },