...

Author: fiftin

docs/admin-guide/cli/migrations.md

@@ -43,7 +43,7 @@ To undo migrations and roll back your database schema to a previous version:
 semaphore migrate --undo-to <version>
 ```
 
-- `<version>`: The migration version you want to roll back to (e.g., `2.13` or `2.14.4`).
+- `<version>` &mdash; The migration version you want to roll back to (e.g., `2.13` or `2.14.4`).
 
 **Example:**
 ```
@@ -52,6 +52,7 @@ semaphore migrate --undo-to 2.13
 
 
 ## Migration from BoltDB to SQLite/MySQL/PostgreSQL
+*Available since version 2.17*
 
 BoltDB was deprecated starting from version 2.16, and many new features introduced in 2.17 are no longer supported by BoltDB. BoltDB support will be fully removed in version 2.19.
 
@@ -61,16 +62,8 @@ To migrate, first update Semaphore to version 2.17 or later, then configure the
 semaphore migrate --from-boltdb /path/to/boltdb/file
 ```
 
-- `/path/to/boltdb/file` &mdash; Path to the existing BoltDB database file.
-
 The command reads all projects, templates, inventories, repositories, keys, users, and task history from BoltDB and writes them into the database specified in the current Semaphore configuration. The original BoltDB file is not modified.
 
-By default, the database schema is migrated to the latest version supported by the current Semaphore binary. You can combine `--from-boltdb` with `--apply-to` or `--undo-to` to target a specific schema version:
-
-```
-semaphore migrate --from-boltdb /path/to/boltdb/file --apply-to 2.17.0
-```
-
 Additional arguments:
 - `--err-log-size=N` &mdash; Maximum number of error lines displayed in the output.
 - `--skip-task-output` &mdash; Do not import task outputs.