dbmate - npm Package Compare versions

Comparing version 2.8.0 to 2.9.0

package.json

 {
   "name": "dbmate",
-  "version": "2.8.0",
+  "version": "2.9.0",
   "description": "A lightweight, framework-agnostic database migration tool",
@@ -27,10 +27,10 @@ "repository": "https://github.com/amacneil/dbmate",
   "optionalDependencies": {
-    "@dbmate/linux-ia32": "2.8.0",
-    "@dbmate/linux-x64": "2.8.0",
-    "@dbmate/linux-arm": "2.8.0",
-    "@dbmate/linux-arm64": "2.8.0",
-    "@dbmate/darwin-x64": "2.8.0",
-    "@dbmate/darwin-arm64": "2.8.0",
-    "@dbmate/win32-x64": "2.8.0"
+    "@dbmate/linux-ia32": "2.9.0",
+    "@dbmate/linux-x64": "2.9.0",
+    "@dbmate/linux-arm": "2.9.0",
+    "@dbmate/linux-arm64": "2.9.0",
+    "@dbmate/darwin-x64": "2.9.0",
+    "@dbmate/darwin-arm64": "2.9.0",
+    "@dbmate/win32-x64": "2.9.0"
   }
 }

README.md

@@ -132,2 +132,3 @@ # Dbmate
 dbmate dump      # write the database schema.sql file
+dbmate load      # load schema.sql file to the database
 dbmate wait      # wait for the database server to become available
@@ -142,2 +143,3 @@ ```
 - `--env, -e "DATABASE_URL"` - specify an environment variable to read the database connection URL from.
+- `--env-file ".env"` - specify an alternate environment variables file(s) to load.
 - `--migrations-dir, -d "./db/migrations"` - where to keep the migration files. _(env: `DBMATE_MIGRATIONS_DIR`)_
@@ -413,3 +415,3 @@ - `--migrations-table "schema_migrations"` - database table to record migrations in. _(env: `DBMATE_MIGRATIONS_TABLE`)_
 
-To dump the `schema.sql` file without performing any other actions, run `dbmate dump`. Unlike other dbmate actions, this command relies on the respective `pg_dump`, `mysqldump`, or `sqlite3` commands being available in your PATH. If these tools are not available, dbmate will silenty skip the schema dump step during `up`, `migrate`, or `rollback` actions. You can diagnose the issue by running `dbmate dump` and looking at the output:
+To dump the `schema.sql` file without performing any other actions, run `dbmate dump`. Unlike other dbmate actions, this command relies on the respective `pg_dump`, `mysqldump`, or `sqlite3` commands being available in your PATH. If these tools are not available, dbmate will silently skip the schema dump step during `up`, `migrate`, or `rollback` actions. You can diagnose the issue by running `dbmate dump` and looking at the output:
 
@@ -416,0 +418,0 @@ ```sh

No alert changes

Improved metrics

Total package byte prevSize

35212

increased by0.52%

Number of lines in readme file

580

increased by0.35%

No dependency changes