revault_api 0.5.0-aarch64-linux → 0.6.0-aarch64-linux

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 38b670c93bf6a7bcd1bda84fb5a976416c7fa56dc1efa822e17a62d089fe1ce4
-  data.tar.gz: dcb4f9f41681fab62ec022662dfab733c497f0635ae0eecee56bcd1247ae7d93
+  metadata.gz: c987414e59a7565309f62571144da164f1106ae169809a5a8f27f21497b61cf4
+  data.tar.gz: 34a972935e1f39b4bd2e15f14e76cb89b4b365456195065e20ffc33a449ab422
 SHA512:
-  metadata.gz: ca0dc813806a148f38623b7d56669c1339bc3d3568227abba7bc441638693a6c794007efb4c141670f71ec1f84772c6ebfd2861287da2deaa0d61b37defeef02
-  data.tar.gz: 4c44c84df1abb5e7de1388019b6482a90d8918cf0ea351a6fe75692f388cd9802dd31139dfe998db3b3132bb8877116f1881ace5295af54915fa08ac09c5478c
+  metadata.gz: c5b74d0171e145409d2a381cfeaad4d9af5a4328f3b31255e756c07806612d9d27855f2892f71829f1f1f6108915e09140789e776345c650a92141563f7d6289
+  data.tar.gz: 3103052d7eb2a8ca5e532f56832295a7b1f3bd7bd860838e510719f9e047cd3810b4b403273c4fa947898e865aa4e49b865a17c478ae80e40b975114fc1f523e

data/README.md

@@ -123,10 +123,10 @@ including its include and exclude rules, is encrypted inside the lockbox and
 travels with it.
 
 ```bash
-lbx secrets.lbox mirror source create --from ./src --to /projects/source
-lbx secrets.lbox mirror source rule add exclude target/** '*.tmp'
-lbx secrets.lbox mirror source status
-lbx secrets.lbox mirror source update
+lbx secrets.lbox mirrors source create --from ./src --to /projects/source
+lbx secrets.lbox mirrors source rules add exclude target/** '*.tmp'
+lbx secrets.lbox mirrors source status
+lbx secrets.lbox mirrors source update
 ```
 
 `status` previews the complete plan; `update` recalculates and applies it.
@@ -163,7 +163,7 @@ See [docs/cli_how_to.md](docs/cli_how_to.md) for command-focused examples.
 Create another local profile:
 
 ```bash
-lockbox vault profile create laptop
+lockbox vault profiles create laptop
 ```
 
 Create an independent encrypted vault with a fresh profile and register that
@@ -185,14 +185,14 @@ material from the current vault.
 List profiles and export a public key:
 
 ```bash
-lockbox vault profile list
-lockbox vault profile export ./laptop.pub --name laptop
+lockbox vault profiles list
+lockbox vault profiles export ./laptop.pub --name laptop
 ```
 
 Import a contact public key after independently verifying its fingerprint:
 
 ```bash
-lockbox vault contact import alice ./alice.pub \
+lockbox vault contacts import alice ./alice.pub \
   --fingerprint <fingerprint> \
   --fingerprint-channel phone-call-to-owner
 ```
@@ -215,7 +215,7 @@ Exporting a private key is supported for backup and migration, but treat the
 output as a secret:
 
 ```bash
-lockbox vault profile backup ./default.profile-backup
+lockbox vault profiles backup ./default.profile-backup
 ```
 
 Private vault keys are stored inside the local vault as secret variable records,
@@ -226,23 +226,22 @@ not as normal files in the vault lockbox. See the CLI help and
 
 Variables are encrypted metadata, not files. They do not appear in file
 listings and are loaded only when variable commands or APIs request them. The
-canonical command is `variable`; `variables` and `var` remain compatibility
-aliases.
+command group is `variables`.
 
 Plain variables are for values that are useful configuration but not high-value
 secrets:
 
 ```bash
-lockbox secrets.lbox variable set DATABASE_URL --value 'postgres://localhost/app'
-lockbox secrets.lbox variable set DATABASE_URL='postgres://localhost/app'
-lockbox secrets.lbox variable get DATABASE_URL
+lockbox secrets.lbox variables set DATABASE_URL --value 'postgres://localhost/app'
+lockbox secrets.lbox variables set DATABASE_URL='postgres://localhost/app'
+lockbox secrets.lbox variables get DATABASE_URL
 ```
 
 With a session-default lockbox, assignment syntax is also supported:
 
 ```bash
-lockbox variable set DATABASE_URL='postgres://localhost/app'
-lockbox variable set DATABASE_URL 'postgres://localhost/app'
+lockbox variables set DATABASE_URL='postgres://localhost/app'
+lockbox variables set DATABASE_URL 'postgres://localhost/app'
 ```
 
 Secret variables are for passwords, API tokens, signing keys, and similar
@@ -250,10 +249,10 @@ material. They use secure-memory handling in the variable path and must be provi
 through an explicit source:
 
 ```bash
-lockbox secrets.lbox variable set --secret API_TOKEN --interactive
-lockbox secrets.lbox variable set --secret API_TOKEN --file ./api-token.txt
-lockbox secrets.lbox variable set --secret API_TOKEN --stdin
-lockbox secrets.lbox variable set --secret API_TOKEN --from-env API_TOKEN
+lockbox secrets.lbox variables set --secret API_TOKEN --interactive
+lockbox secrets.lbox variables set --secret API_TOKEN --file ./api-token.txt
+lockbox secrets.lbox variables set --secret API_TOKEN --stdin
+lockbox secrets.lbox variables set --secret API_TOKEN --from-env API_TOKEN
 ```
 
 Avoid passing secrets as command-line arguments. Shell history and process

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: revault_api
 version: !ruby/object:Gem::Version
-  version: 0.5.0
+  version: 0.6.0
 platform: aarch64-linux
 authors:
 - OnePub
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-10-14 00:00:00.000000000 Z
+date: 2026-10-24 00:00:00.000000000 Z
 dependencies: []
 description: Complete class-based reVault lockbox and vault API
 email: