postman-cli 1.65.0 → 1.66.0

package/man/postman.1

@@ -1,4 +1,4 @@
-.TH POSTMAN 1 "2026-09-25" "v1.65.0" "Postman CLI Manual"
+.TH POSTMAN 1 "2026-09-28" "v1.66.0" "Postman CLI Manual"
 .SH NAME
 postman \- Command\-line companion utility for Postman
 .SH SYNOPSIS
@@ -860,7 +860,7 @@ Specify a data file to use for iterations (either JSON or CSV)
 [BETA] Name or id of the view to execute (within \-\-iteration\-data\-dataset). The view's result set drives one iteration per row.
 .TP
 .B \-\-dataset <pathOrDir>
-[BETA] Pass \-\-dataset multiple times to load several .dataset.yaml files (or directories containing them). Each is made available to scripts as pm.datasets(<id>). When provided, auto\-discovery of .dataset.yaml files from the collection's parent repo is disabled. For a cloud collection, scripts address cloud datasets by id via pm.datasets(<id>) (resolved from your `postman login` session). SECURITY: for a cloud collection this does NOT scope access — a script can pm.datasets(<anyId>) for any dataset your session can read. Only run collections you trust against a logged\-in cloud session. (default: )
+[BETA] Pass \-\-dataset multiple times to load several .dataset.yaml files (or directories containing them). Each is made available to collection scripts and local mock handlers as pm.datasets(<id>). When provided, auto\-discovery of .dataset.yaml files from the collection's parent repo is disabled. For a cloud collection, scripts address cloud datasets by id via pm.datasets(<id>) (resolved from your `postman login` session). SECURITY: for a cloud collection this does NOT scope access — a script can pm.datasets(<anyId>) for any dataset your session can read. Only run collections you trust against a logged\-in cloud session. (default: )
 .TP
 .B \-i <id>
 Specify the request/folder id, name, or path to run from the collection. Use a path (e.g. "FolderName/RequestName") to disambiguate items with the same name. Can be specified multiple times to run multiple items (default: )
@@ -1446,6 +1446,9 @@ Generate artifacts from a specification.
 .TP
 .B spec sync
 Sync a generated collection with its source specification.
+.TP
+.B spec delete
+Delete a spec by its cloud ID or local file path. Cannot be undone.
 
 .SS "spec lint"
 Run linting on the given specification by ID or local file path.
@@ -1708,12 +1711,16 @@ Workspace ID (cloud mode)
 .TP
 .B \-\-api\-key <key>
 Postman API key
+.TP
+.B \-\-force
+Overwrite the collection if one with this name already exists (local mode)
 
 .TP Examples:
 
 Examples:
   postman spec generate collection ./openapi.yaml \-n "My API"
   postman spec generate collection ./openapi.yaml \-n "My API" \-\-folder\-strategy Tags
+  postman spec generate collection ./openapi.yaml \-n "My API" \-\-force
   postman spec generate collection 12345678\-abcd\-1234\-abcd\-1234567890ab \-n "My API"
 
 
@@ -1751,6 +1758,29 @@ Examples:
 
 
 
+.SS "spec delete"
+Delete a spec by its cloud ID or local file path. Cannot be undone.
+
+.B Usage:
+<spec> [options]
+
+.B Options:
+.TP
+.B \-y, \-\-yes
+Delete without asking for confirmation first
+.TP
+.B \-\-api\-key <key>
+Postman API key, used with a cloud ID (defaults to your `postman login` session)
+
+.TP Examples:
+
+Examples:
+  postman spec delete 12345678\-90ab\-cdef\-1234\-567890abcdef
+  postman spec delete ./postman/specs/pet\-store
+  postman spec delete ./postman/specs/pet\-store/index.yaml \-\-yes
+
+
+
 .SS "monitor"
 Run and manage Postman monitors.
 
@@ -2753,6 +2783,9 @@ Example: less_than(p95, 500) or less_than(error_rate, 5)
 .B \-\-use\-mock <mapping>
 Redirect a variable/host to a local code mock or cloud Mock Server (repeatable). 
 Format: "<{{var}}|host> mock|mock\-server:<path|id> [scenario]" (default: )
+.TP
+.B \-\-dataset <pathOrDir>
+Pass \-\-dataset multiple times to load several .dataset.yaml files (or directories containing them). Each is made available to the handlers of the local mocks started by \-\-use\-mock as pm.datasets(<id>). Local runner only. (default: )
 
 .TP Examples:
 
@@ -2762,6 +2795,7 @@ Examples:
   postman performance run 123456\-45159473\-1e45\-1f34\-5678\-1234567890ab \-\-runner local \-\-setup\-collection 123456\-11111111\-1111\-4111\-8111\-111111111111 \-\-teardown\-collection 123456\-22222222\-2222\-4222\-8222\-222222222222
   postman performance run 123456\-45159473\-1e45\-1f34\-5678\-1234567890ab \-\-runner postman\-cloud \-\-setup\-collection 123456\-11111111\-1111\-4111\-8111\-111111111111 \-\-teardown\-collection 123456\-22222222\-2222\-4222\-8222\-222222222222
   postman performance run 123456\-45159473\-1e45\-1f34\-5678\-1234567890ab \-\-runner postman\-cloud\-static\-ip
+  postman performance run 123456\-45159473\-1e45\-1f34\-5678\-1234567890ab \-\-use\-mock "{{baseUrl}} mock:./postman/mocks/orders" \-\-dataset ./postman/datasets/Orders
 
 
 .SS "performance list"
@@ -3940,6 +3974,9 @@ Workspace that owns the run, for recording its start history. Auto\-resolved for
 .TP
 .B \-\-no\-history
 Do not record this run in the mock's start history.
+.TP
+.B \-\-dataset <pathOrDir>
+Pass \-\-dataset multiple times to load several .dataset.yaml files (or directories containing them). Each is made available to the mock's handlers as pm.datasets(<id>). (default: )
 
 .TP Examples:
 
@@ -3949,6 +3986,7 @@ Eg. postman mock run 12345678\-90ab\-cdef\-1234\-567890abcdef  # by id, from Pos
     postman mock run ./postman/mocks/orders \-\-port auto    # pick any free port
     postman mock run ./postman/mocks/orders \-\-port 4600    # use port 4600 (fails if it is in use)
     postman mock run ./postman/mocks/orders \-\-workspace <id>  # record start history for a path run
+    postman mock run ./postman/mocks/orders \-\-dataset ./postman/datasets/Orders
 
 Eligible runs are recorded in the mock's start history (source: cli) so they appear under
 "Previous starts" in Postman. Cloud ids record automatically; a manifest\-backed path run needs
@@ -6441,6 +6479,9 @@ Materialise the dependencies declared in .postman/resources.yaml (all, or one).
 .TP
 .B dependency update
 Refresh declared dependencies to the latest content from their source (all, or one).
+.TP
+.B dependency remove
+Remove a workspace dependency and delete its local files.
 
 .SS "dependency add"
 Add a Postman collection, environment, or mock as a workspace dependency.
@@ -6545,6 +6586,36 @@ Examples:
 
 
 
+.SS "dependency remove"
+Remove a workspace dependency and delete its local files.
+
+.B Usage:
+[options] <nameOrId>
+
+.B Options:
+.TP
+.B \-\-type <type>
+Only match dependencies of this type (collection, environment, or mock).
+.TP
+.B \-y, \-\-yes
+Skip the confirmation prompt (required outside an interactive terminal).
+.TP
+.B \-\-json
+Output the result as JSON.
+
+.TP Examples:
+
+A <nameOrId> is the cloud id, display name, or on\-disk name of a declared dependency
+(as shown by `postman dependency list`). Removing a collection also removes the
+environments pinned to it, unless another collection pins them too.
+
+Examples:
+  postman dependency remove "My Collection"
+  postman dependency remove 844951\-51ea04bb\-8d1a\-439e\-aa70\-fe91852efcda \-\-yes
+  postman dependency remove Prod \-\-type environment \-\-yes \-\-json
+
+
+
 .SH SEE ALSO
 Full documentation: https://learning.postman.com/docs/postman\-cli/postman\-cli\-overview/
 .SH AUTHOR

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "postman-cli",
-  "version": "1.65.0",
+  "version": "1.66.0",
   "description": "Official Postman CLI - Command-line companion for API development, testing, and automation",
   "keywords": [
     "postman",
@@ -62,10 +62,10 @@
     "scripts/"
   ],
   "optionalDependencies": {
-    "@postman/pm-bin-macos-arm64": "1.65.0",
-    "@postman/pm-bin-macos-x64": "1.65.0",
-    "@postman/pm-bin-linux-x64": "1.65.0",
-    "@postman/pm-bin-linux-arm64": "1.65.0",
-    "@postman/pm-bin-windows-x64": "1.65.0"
+    "@postman/pm-bin-macos-arm64": "1.66.0",
+    "@postman/pm-bin-macos-x64": "1.66.0",
+    "@postman/pm-bin-linux-x64": "1.66.0",
+    "@postman/pm-bin-linux-arm64": "1.66.0",
+    "@postman/pm-bin-windows-x64": "1.66.0"
   }
 }