@proggarapsody/bitbottle 1.40.0 → 1.42.0

package/README.md

@@ -47,6 +47,11 @@ bitbottle skill remove             # uninstall
 go install github.com/proggarapsody/bitbottle/cmd/bitbottle@latest
 ```
 
+**Nix:**
+```sh
+nix run github:proggarapsody/bitbottle -- --version
+```
+
 **Homebrew / binary / deb / rpm / Docker** — see the [latest release](https://github.com/proggarapsody/bitbottle/releases/latest).
 
 ---
@@ -231,16 +236,17 @@ bitbottle environment create MYWORKSPACE/my-service --name "Prod" --type Product
 # Delete an environment (destructive — --confirm required on non-TTY)
 bitbottle environment delete MYWORKSPACE/my-service {env-uuid} --confirm
 
-# Environment variables (secured values show as <secured>)
-bitbottle environment variable list   MYWORKSPACE/my-service {env-uuid}
-bitbottle environment variable set    MYWORKSPACE/my-service {env-uuid} DEPLOY_KEY prod-val
-bitbottle environment variable set    MYWORKSPACE/my-service {env-uuid} API_TOKEN secret --secured
-bitbottle environment variable delete MYWORKSPACE/my-service {env-uuid} {var-uuid}
+# Environment variables — use variable --scope deployment (see deprecation note below)
+bitbottle variable list   MYWORKSPACE/my-service --scope deployment --env {env-uuid}
+bitbottle variable set    MYWORKSPACE/my-service DEPLOY_KEY prod-val --scope deployment --env {env-uuid}
+bitbottle variable set    MYWORKSPACE/my-service API_TOKEN secret --scope deployment --env {env-uuid} --secured
+bitbottle variable delete MYWORKSPACE/my-service DEPLOY_KEY --scope deployment --env {env-uuid} --confirm
 ```
 
-All commands support `--json fields` and `--jq expr`. Variable `delete` takes
-the variable UUID (not the key) — run `environment variable list --json uuid,key`
-to find it. Secured variable values are never returned by the API once set.
+All commands support `--json fields` and `--jq expr`. Secured variable values
+are never returned by the API once set.
+
+**`environment variable *` is deprecated.** Use `bitbottle variable --scope deployment --env ENV-UUID` instead. The old commands still work but print a deprecation warning.
 
 These commands return a typed unsupported-capability error on Bitbucket Server /
 Data Center — deployments and environments are a Cloud-only feature.
@@ -475,6 +481,11 @@ bitbottle commit comment delete MYPROJ/my-service abc1234 1234
 # Structured output
 bitbottle commit comment list MYPROJ/my-service abc1234 --json id,author,body
 bitbottle commit comment list MYPROJ/my-service abc1234 --jq '.[].body'
+
+# Emoji reactions (Bitbucket Server / DC only)
+bitbottle commit comment list MYPROJ/my-service abc1234 --reactions   # adds REACTIONS column
+bitbottle commit comment react   MYPROJ/my-service abc1234 1234 --emoji thumbs_up
+bitbottle commit comment unreact MYPROJ/my-service abc1234 1234 --emoji thumbs_up
 ```
 
 On Bitbucket Server / Data Center, `edit` and `delete` use optimistic

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@proggarapsody/bitbottle",
-  "version": "1.40.0",
+  "version": "1.42.0",
   "description": "Bitbucket CLI for Server/Data Center and Cloud — npm wrapper for bitbottle",
   "keywords": [
     "mcp",