@proggarapsody/bitbottle 1.39.0 → 1.41.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +14 -8
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -231,16 +231,17 @@ bitbottle environment create MYWORKSPACE/my-service --name "Prod" --type Product
231
231
  # Delete an environment (destructive — --confirm required on non-TTY)
232
232
  bitbottle environment delete MYWORKSPACE/my-service {env-uuid} --confirm
233
233
 
234
- # Environment variables (secured values show as <secured>)
235
- bitbottle environment variable list MYWORKSPACE/my-service {env-uuid}
236
- bitbottle environment variable set MYWORKSPACE/my-service {env-uuid} DEPLOY_KEY prod-val
237
- bitbottle environment variable set MYWORKSPACE/my-service {env-uuid} API_TOKEN secret --secured
238
- bitbottle environment variable delete MYWORKSPACE/my-service {env-uuid} {var-uuid}
234
+ # Environment variables — use variable --scope deployment (see deprecation note below)
235
+ bitbottle variable list MYWORKSPACE/my-service --scope deployment --env {env-uuid}
236
+ bitbottle variable set MYWORKSPACE/my-service DEPLOY_KEY prod-val --scope deployment --env {env-uuid}
237
+ bitbottle variable set MYWORKSPACE/my-service API_TOKEN secret --scope deployment --env {env-uuid} --secured
238
+ bitbottle variable delete MYWORKSPACE/my-service DEPLOY_KEY --scope deployment --env {env-uuid} --confirm
239
239
  ```
240
240
 
241
- All commands support `--json fields` and `--jq expr`. Variable `delete` takes
242
- the variable UUID (not the key) run `environment variable list --json uuid,key`
243
- to find it. Secured variable values are never returned by the API once set.
241
+ All commands support `--json fields` and `--jq expr`. Secured variable values
242
+ are never returned by the API once set.
243
+
244
+ **`environment variable *` is deprecated.** Use `bitbottle variable --scope deployment --env ENV-UUID` instead. The old commands still work but print a deprecation warning.
244
245
 
245
246
  These commands return a typed unsupported-capability error on Bitbucket Server /
246
247
  Data Center — deployments and environments are a Cloud-only feature.
@@ -475,6 +476,11 @@ bitbottle commit comment delete MYPROJ/my-service abc1234 1234
475
476
  # Structured output
476
477
  bitbottle commit comment list MYPROJ/my-service abc1234 --json id,author,body
477
478
  bitbottle commit comment list MYPROJ/my-service abc1234 --jq '.[].body'
479
+
480
+ # Emoji reactions (Bitbucket Server / DC only)
481
+ bitbottle commit comment list MYPROJ/my-service abc1234 --reactions # adds REACTIONS column
482
+ bitbottle commit comment react MYPROJ/my-service abc1234 1234 --emoji thumbs_up
483
+ bitbottle commit comment unreact MYPROJ/my-service abc1234 1234 --emoji thumbs_up
478
484
  ```
479
485
 
480
486
  On Bitbucket Server / Data Center, `edit` and `delete` use optimistic
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@proggarapsody/bitbottle",
3
- "version": "1.39.0",
3
+ "version": "1.41.0",
4
4
  "description": "Bitbucket CLI for Server/Data Center and Cloud — npm wrapper for bitbottle",
5
5
  "keywords": [
6
6
  "mcp",