chore: bump to 2.0.0

Author: markcda

CHANGELOG.md

@@ -7,6 +7,26 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.0.0] - 2025-11-06
+
+### Added
+
+- `from_cmd` variable type (for example, to get some passkeys via `curl` requests, etc.).
+- `desc` (description) field to `exists`, `exists_any` & `check_success` requirements to optionally describe steps for resolving them.
+- Independent variable setup for each pipelines (inside `depl edit project` UI -> any pipeline -> `Setup variables for the pipeline`).
+- `depl use` command to use content or templates from Deployer's storage.
+- `depl export/import registries` command (exports all actions and pipelines, and imports with merge).
+
+### Changed
+
+- Extended command-line options for `depl new content`, unified `edit`/`cat`/`rm` behavior.
+- Changed description output for `depl ls pipelines`.
+
+### Fixed
+
+- Custom storage path by `DEPLOYER_STORAGE_PATH` env variable wasn't applied by first.
+- Actions that used in a selected pipeline from the Registry are now synchronized with project config file.
+
 ## [2.0.0-beta-3] - 2025-10-21
 
 ### Changed
@@ -569,6 +589,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Build support.
 - TUI.
 
+[2.0.0]:          https://github.com/impulse-sw/deployer/compare/2.0.0-beta-3...2.0.0
 [2.0.0-beta-3]:   https://github.com/impulse-sw/deployer/compare/1.5.0-1...2.0.0-beta-3
 [1.5.0-1]:        https://github.com/impulse-sw/deployer/compare/1.5.0...1.5.0-1
 [1.5.0]:          https://github.com/impulse-sw/deployer/compare/1.4.4...1.5.0

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "deployer"
-version = "2.0.0-beta-8"
+version = "2.0.0"
 edition = "2024"
 
 [[bin]]

DOCS.md

@@ -17,15 +17,28 @@ Typically, it runs in a separate folder to save the cache while keeping the code
 Deployer is primarily a CLI utility. You can see help for any Deployer command by specifying the `-h` option. Here are some examples of the most common commands:
 
 ```bash
-depl new action                            # create an Action and put in Registry
-depl new pipeline                          # create a Pipeline and put in Registry
+depl new action                            # create an action and put in Registry
+depl new pipeline                          # create a pipeline and put in Registry
+depl new content                           # add some content in Deployer's storage folder
 depl new remote                            # add new remote host to Registry
+
+depl ls actions/pipelines/content/remote   # list all entities from Registries
+depl cat action/pipeline/content/remote    # display information about entiry from Registry
+depl rm action/pipeline/content/remote     # remove entity from Registry
+
 depl init                                  # init project, fill all attributes
 
+depl edit project                          # edit project
+depl edit .                                # (the same)
+
 depl with                                  # check compatibility and assign Pipeline to project,
                                            # also specify needed variables and artifacts
 
+depl use                                   # use some content from Deployer's storage
+
 depl run                                   # run default Pipeline
+depl                                       # (the same)
+
 depl run my-pipe                           # run specified `my-pipe` Pipeline
 depl run configure,build -o build-folder   # run `configure` and `build` Pipelines in a `build-folder`
 depl run -R my-remote my-pipe              # run `my-pipe` Pipeline on remote host `my-remote`
@@ -75,14 +88,17 @@ requirements:
       - /bin/upx
       - /usr/bin/upx
       - ~/.local/bin/upx
+    desc: "This is optional description with information about UPX installation steps."
   # if this path exists, the requirement is considered satisfied
   - type: exists
     path: /usr/bin/mold
+    desc: "Only optional"
   # if this check is passed, the requirement will be considered satisfied (for details, see below - action `Check`)
   - type: check_success
     command:
       cmd: /usr/bin/python -V
     success_when_found: "Python 3."
+    desc: "Only optional"
   # if a given remote host exists in the Registry, is accessible, and its Deployer version is identical to the version of the running Deployer,
   # the requirement will be considered satisfied
   - type: remote_accessible_and_ready

TODO.md

@@ -1,37 +1,3 @@
-# `deployer`'s 2.0 TODO list
+# `deployer`'s TODO list
 
-- [~] TUI for editing containered (Docker/Podman), Ansible, GitHub CI/CD and GitLab CI/CD options for Pipelines
-- [x] Replace complete `RemoteHost` definitions from `ansible_opts` for their shortnames
-- [x] Add `depl cd` command to change current directory to one of run directories
-- [x] Make `depl export` command:
-  1. [x] for exporting Pipelines to `bash` scripts
-  2. [x] for exporting (and importing with merging) actions & Pipelines Registries
-  3. [x] for exporting Pipelines to CI/CD (GitHub Actions & GitLab CI) configurations
-- [x] Add `--skip N` argument to skip N actions inside selected Pipelines, if you exactly know that they have no need to re-run after changes
-- [x] Add `--no-clear` argument to disable screen clear on `run`/`watch`
-- [x] Go to more declarative way to define project configuration (ver. 7 & Deployer v2.0)
-  1. [x] Remove targets, programming languages and actions variability
-  2. [x] Rename `Actions` & `Pipelines` to `actions` and `pipelines`
-  3. [x] Split `configs.rs` to `project.rs` and `globals.rs`
-  4. [x] Allow to both use and define actions in pipelines. Used actions should be defined inside project configuration
-  5. [x] Fix all traits and TUI interface
-  6. [x] Fix action setup:
-    > Action setup depends on command definition of placeholders and replacements. I think I should remove replacements completely
-    > and add `with` field to `UsedAction` as `BTreeMap<String, Variable>`, e.g. placeholder-variable pairs.
-- [x] Remove `artifacts` field completely (`artifacts_placements` is enough)
-- [x] Fix `depl watch` with no `artifacts` folder ignoring
-- [x] Remove automigrator with `MIGRATIONS.md` autoreference:
-  1. [-] Add `depl migrate` command
-  2. [x] Remove `configs` source
-  3. [x] Refine `read` functions from `crate::rw` module
-  4. [x] Add prompt on `crate::rw` to read `MIGRATIONS.md`
-- [-] Make `DEPLOYER_DRIVER` env variable support to define executor: bash on itself or Deployer implementation (default)
-- [x] Make `driver` pipeline option support to define executor: bash on itself or Deployer implementation (default):
-  1. [x] For Pipelines
-  2. [x] For containered builds & runs
-  3. [x] For Ansible runs
-- [x] Fix issue which causes not to adding actions definitions when using a pipeline from the registry, to the project config
-- [x] Add `info` field to requirements to inform users about commands or links to install them
-- [x] Unify `edit`, `cat` & `rm` commands behavior
-- [x] Add possibility to setup variables inside each pipeline independently
-- [x] Add `use` command to synchronize content (with `subfolder` argument)
+- [~] TUI for editing containered (Docker/Podman), Ansible, GitHub CI/CD and GitLab CI/CD options for pipelines