postman-cli 1.43.0 → 1.45.0

package/man/postman.1

@@ -1,4 +1,4 @@
-.TH POSTMAN 1 "2026-07-15" "v1.43.0" "Postman CLI Manual"
+.TH POSTMAN 1 "2026-07-30" "v1.45.0" "Postman CLI Manual"
 .SH NAME
 postman \- Command\-line companion utility for Postman
 .SH SYNOPSIS
@@ -172,14 +172,14 @@ Define the number of iterations to run
 .B \-d, \-\-iteration\-data <path>
 Specify a data file to use for iterations (either JSON or CSV)
 .TP
-.B \-\-iteration\-data\-dataset <path>
-[BETA] Path to a .dataset.yaml whose view drives the iteration data. Mutually exclusive with \-\-iteration\-data. Requires \-\-iteration\-data\-view.
+.B \-\-iteration\-data\-dataset <pathOrId>
+[BETA] Path to a .dataset.yaml (local collection) or a cloud dataset id (cloud collection) whose view drives the iteration data. Mutually exclusive with \-\-iteration\-data. Requires \-\-iteration\-data\-view.
 .TP
 .B \-\-iteration\-data\-view <nameOrId>
 [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. (default: )
+[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: )
 .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: )
@@ -491,49 +491,76 @@ Manage workspace resources.
 
 .B Subcommands:
 .TP
+.B workspace list
+List all available Postman Workspaces
+.TP
 .B workspace prepare
 Prepare local collections and environments for push by validating and regenerating IDs if needed.
 .TP
 .B workspace push
-Push local collection, environment, specification, mock, and simulation changes to Postman workspace.
+Push local workspace entities (collections, environments, specifications, and more) to Postman workspace.
 
-.SS "workspace prepare"
-Prepare local collections and environments for push by validating and regenerating IDs if needed.
+.SS "workspace list"
+List all available Postman Workspaces
 
 .B Usage:
 [options]
 
 .B Options:
 .TP
-.B \-\-collections\-dir <path>
-Path to the collections directory (default: postman/collections)
+.B \-f, \-\-filter <name>
+Filter workspaces by name.
 .TP
-.B \-\-environments\-dir <path>
-Path to the environments directory (default: postman/environments)
+.B \-t, \-\-type <type>
+Filter workspaces by visibility type: team, public, private, personal.
+.TP
+.B \-\-verbose
+Verbose output
+.TP
+.B \-\-debug
+Debug output
+.TP
+.B \-\-json
+JSON output
+
+.TP Examples:
+
+Examples:
+  postman workspace list
+  postman workspace list \-\-filter "my\-workspace"
+  postman workspace list \-\-type team
+  postman workspace list \-\-type team \-\-filter "project"
+
+
+
+.SS "workspace prepare"
+Prepare local collections and environments for push by validating and regenerating IDs if needed.
+
+.B Usage:
+[options]
+
+.B Options:
 .TP
 .B \-\-verbose
 Show detailed logging
 
 .SS "workspace push"
-Push local collection, environment, specification, mock, and simulation changes to Postman workspace.
+Push local workspace entities (collections, environments, specifications, and more) to Postman workspace.
 
 .B Usage:
 [options]
 
 .B Options:
 .TP
-.B \-\-collections\-dir <path>
-Path to the collections directory (default: postman/collections)
-.TP
-.B \-\-environments\-dir <path>
-Path to the environments directory (default: postman/environments)
-.TP
 .B \-\-no\-prepare
 Skip ID validation and auto\-fix before pushing
 .TP
 .B \-y, \-\-yes
 Skip all confirmation prompts
 .TP
+.B \-\-push\-strategy <strategy>
+Push strategy. "force\-sync": mirror the whole workspace — also DELETE cloud entities that have no local counterpart (destructive). Defaults to "default" (create/update only).
+.TP
 .B \-\-verbose
 Show detailed logging
 .TP
@@ -1228,7 +1255,7 @@ Generate and manage your SDKs directly from the command line.
 Create or update .postman/config.json with an SDK configuration stub.
 .TP
 .B sdk generate
-Generate a new SDK from a Postman collection or specification.
+Generate a new SDK from a Postman collection or specification (OpenAPI or AsyncAPI).
 .TP
 .B sdk track
 Enable change tracking for a generated SDK. Adds file hashes to .manifest.json so that the next `sdk generate` can detect your edits and preserve them via 3\-way merge.
@@ -1257,7 +1284,7 @@ Create or update .postman/config.json with an SDK configuration stub.
 Skip prompts and overwrite existing sdk config
 
 .SS "sdk generate"
-Generate a new SDK from a Postman collection or specification.
+Generate a new SDK from a Postman collection or specification (OpenAPI or AsyncAPI).
 
 .B Usage:
 <idOrPath> [options]
@@ -1317,6 +1344,8 @@ Input:
     \- A file path to a collection (.json) or specification (.json, .yaml, .yml) file
     \- A URL to a publicly accessible collection or specification file
   
+  Supported specification formats: OpenAPI (2.0/3.x) and AsyncAPI (2.x/3.x).
+  
   When using an ID, the SDK generation updates the version in Postman Cloud.
   When using a file path or URL, a one\-off build is created that does not update the Postman Cloud.
   
@@ -1336,6 +1365,9 @@ Examples:
   Generate SDK from OpenAPI specification file (one\-off build):
     postman sdk generate ./openapi.yaml \-l typescript \-o ./my\-sdk
 
+  Generate SDK from AsyncAPI specification file (one\-off build):
+    postman sdk generate ./asyncapi.yaml \-l typescript \-o ./my\-sdk
+
   Generate SDK from publicly accessible URL (one\-off build):
     postman sdk generate https://petstore.swagger.io/v2/swagger.json \-l typescript \-o ./my\-sdk
 
@@ -2727,19 +2759,19 @@ Examples:
 .B Subcommands:
 .TP
 .B dataset list
-[BETA] List dataset YAMLs under the given directory, or print summary for a single YAML file.
+[BETA] List local dataset YAMLs under a path, or (no path) a workspace's cloud datasets.
 .TP
 .B dataset get
-[BETA] Print a dataset's metadata and structure summary.
+[BETA] Print a dataset's metadata and structure summary (local YAML path or cloud id).
 .TP
 .B dataset query
-[BETA] Run an ad\-hoc SQL query against a dataset.
+[BETA] Run an ad\-hoc SQL query against a dataset (local YAML path or cloud id).
 .TP
 .B dataset create
-[BETA] Scaffold a new empty .dataset.yaml file at <path>.
+[BETA] Scaffold a new .dataset.yaml at <path>, or (no path, with \-w) create a cloud dataset.
 .TP
 .B dataset delete
-[BETA] Permanently remove a dataset's .dataset.yaml file and its .resources/ directory.
+[BETA] Permanently remove a dataset: a local .dataset.yaml (+ .resources/) or a cloud dataset id.
 .TP
 .B dataset source
 [BETA] Inspect and manage a dataset's datasources.
@@ -2748,13 +2780,19 @@ Examples:
 [BETA] Inspect and manage saved views on a dataset.
 
 .SS "dataset list"
-[BETA] List dataset YAMLs under the given directory, or print summary for a single YAML file.
+[BETA] List local dataset YAMLs under a path, or (no path) a workspace's cloud datasets.
 
 .B Usage:
-[options] <pathOrDir>
+[options] [pathOrDir]
 
 .B Options:
 .TP
+.B \-w, \-\-workspace <id>
+Postman workspace ID (cloud list)
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
+.TP
 .B \-\-json
 Output as JSON instead of a table
 
@@ -2763,32 +2801,40 @@ Output as JSON instead of a table
 Examples:
   postman dataset list ./postman/datasets
   postman dataset list ./postman/datasets/users/users.dataset.yaml
+  postman dataset list \-w 12345678\-90ab\-cdef\-1234\-567890abcdef
 
 
 
 .SS "dataset get"
-[BETA] Print a dataset's metadata and structure summary.
+[BETA] Print a dataset's metadata and structure summary (local YAML path or cloud id).
 
 .B Usage:
-[options] <path>
+[options] <datasetPathOrId>
 
 .B Options:
 .TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
+.TP
+.B \-\-no\-populate
+Skip fetching datasources/views for a cloud dataset
+.TP
 .B \-\-json
-Output the full parsed YAML as JSON
+Output the full dataset as JSON
 
 .TP Examples:
 
 Examples:
   postman dataset get ./postman/datasets/users/users.dataset.yaml
+  postman dataset get 14e30f6c\-1234\-1234\-1234\-cafef00dc0de
 
 
 
 .SS "dataset query"
-[BETA] Run an ad\-hoc SQL query against a dataset.
+[BETA] Run an ad\-hoc SQL query against a dataset (local YAML path or cloud id).
 
 .B Usage:
-[options] <path>
+[options] <datasetPathOrId>
 
 .B Options:
 .TP
@@ -2798,6 +2844,9 @@ SQL query to execute (e.g. "SELECT * FROM source_users LIMIT 10")
 .B \-p, \-\-param <value...>
 Positional parameter values for $1, $2, ... bindings; repeatable
 .TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
+.TP
 .B \-\-json
 Output rows as JSON instead of a table
 
@@ -2806,14 +2855,15 @@ Output rows as JSON instead of a table
 Examples:
   postman dataset query ./users.dataset.yaml \-q "SELECT * FROM source_users LIMIT 5"
   postman dataset query ./users.dataset.yaml \-q "SELECT * FROM source_users WHERE id = $1" \-p 42
+  postman dataset query 14e30f6c\-1234\-1234\-1234\-cafef00dc0de \-q "SELECT * FROM users LIMIT 5"
 
 
 
 .SS "dataset create"
-[BETA] Scaffold a new empty .dataset.yaml file at <path>.
+[BETA] Scaffold a new .dataset.yaml at <path>, or (no path, with \-w) create a cloud dataset.
 
 .B Usage:
-[options] <path>
+[options] [path]
 
 .B Options:
 .TP
@@ -2823,24 +2873,31 @@ Human\-readable name for the dataset
 .B \-d, \-\-description <desc>
 Optional description
 .TP
-.B \-\-id <uuid>
-Override the generated dataset id (defaults to a random v4 UUID)
+.B \-\-dataset\-id <uuid>
+Override the generated dataset id (local only; defaults to a random v4 UUID)
 .TP
 .B \-\-force
 Overwrite an existing file at <path>
+.TP
+.B \-w, \-\-workspace <id>
+Postman workspace ID (create a cloud dataset)
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
 
 .TP Examples:
 
 Examples:
   postman dataset create ./postman/datasets/users/users.dataset.yaml \-\-name "Users"
+  postman dataset create \-\-name "Users" \-w 12345678\-90ab\-cdef\-1234\-567890abcdef
 
 
 
 .SS "dataset delete"
-[BETA] Permanently remove a dataset's .dataset.yaml file and its .resources/ directory.
+[BETA] Permanently remove a dataset: a local .dataset.yaml (+ .resources/) or a cloud dataset id.
 
 .B Usage:
-[options] <path>
+[options] <datasetPathOrId>
 
 .B Options:
 .TP
@@ -2848,13 +2905,17 @@ Examples:
 Skip the confirmation prompt
 .TP
 .B \-\-keep\-resources
-Delete only the YAML file; leave the .resources/ directory intact
+Delete only the YAML file; leave the .resources/ directory intact (local only)
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
 
 .TP Examples:
 
 Examples:
   postman dataset delete ./postman/datasets/users/users.dataset.yaml
   postman dataset delete ./postman/datasets/users/users.dataset.yaml \-\-yes
+  postman dataset delete 14e30f6c\-1234\-1234\-1234\-cafef00dc0de \-\-yes
 
 
 
@@ -2867,32 +2928,39 @@ Examples:
 .B Subcommands:
 .TP
 .B dataset source list
-[BETA] List the datasources defined on a dataset.
+[BETA] List the datasources defined on a dataset (local YAML path or cloud id).
 .TP
 .B dataset source add
 [BETA] Add a datasource to a dataset.
 .TP
 .B dataset source remove
-[BETA] Remove a datasource from a dataset.
+[BETA] Remove a datasource from a dataset (local YAML path or cloud id).
 .TP
 .B dataset source update
 [BETA] Update fields on an existing datasource. Only the flags you provide are changed.
 
 .SS "dataset source list"
-[BETA] List the datasources defined on a dataset.
+[BETA] List the datasources defined on a dataset (local YAML path or cloud id).
 
 .B Usage:
-[options] <path>
+[options]
 
 .B Options:
 .TP
+.B \-d, \-\-dataset <datasetPathOrId>
+Dataset whose sources to list — a local .dataset.yaml path or a cloud dataset id
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
+.TP
 .B \-\-json
 Output sources as JSON instead of a table
 
 .TP Examples:
 
 Examples:
-  postman dataset source list ./postman/datasets/users/users.dataset.yaml
+  postman dataset source list \-d ./postman/datasets/users/users.dataset.yaml
+  postman dataset source list \-d 14e30f6c\-1234\-1234\-1234\-cafef00dc0de
 
 
 
@@ -2900,14 +2968,17 @@ Examples:
 [BETA] Add a datasource to a dataset.
 
 .B Usage:
-[options] <pathOrId>
+[options]
 
 .B Options:
 .TP
+.B \-d, \-\-dataset <datasetPathOrId>
+Dataset to add the source to — a local .dataset.yaml path or a cloud dataset id
+.TP
 .B \-n, \-\-name <name>
 Logical name for the source (becomes the SQL table name)
 .TP
-.B \-\-id <uuid>
+.B \-\-source\-id <uuid>
 Override the generated source id
 .TP
 .B \-\-format <csv|json|mysql|postgres>
@@ -2920,10 +2991,13 @@ Source kind; inferred from \-\-file/\-\-url when omitted
 Path to a local CSV/JSON file (absolute or cwd\-relative)
 .TP
 .B \-\-ref\-only
-Reference the file in place; do NOT copy into data_dir
+Reference the file in place; do NOT copy into data_dir (local dataset)
 .TP
 .B \-\-force
-When copying, overwrite an existing file at the destination
+When copying, overwrite an existing file at the destination (local dataset)
+.TP
+.B \-\-upload
+Cloud dataset only: upload \-\-file as a postmancloudfile source (runs via /exec). Without \-\-upload, \-\-file is registered as a local_filesystem csv/json source read by the local engine.
 .TP
 .B \-\-url <url>
 HTTP(S) URL to a remote CSV/JSON file
@@ -2938,7 +3012,7 @@ DB port
 DB user (warning: stored as plaintext in the YAML).
 .TP
 .B \-\-password <password>
-DB password (warning: stored as plaintext in the YAML).
+DB password. WARNING: passing it here exposes it in `ps` output and shell history, and it is stored as plaintext in the dataset YAML (local) or sent in the request body (cloud). Prefer a restricted DB user; secure input (prompt / stdin / env) is planned.
 .TP
 .B \-\-database <db>
 DB database name
@@ -2948,18 +3022,30 @@ DB table name (optional)
 .TP
 .B \-\-slug <slug>
 Optional slug for the source
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
 
 .SS "dataset source remove"
-[BETA] Remove a datasource from a dataset.
+[BETA] Remove a datasource from a dataset (local YAML path or cloud id).
 
 .B Usage:
-[options] <path> <sourceNameOrId>
+[options] <sourceNameOrId>
+
+.B Options:
+.TP
+.B \-d, \-\-dataset <datasetPathOrId>
+Dataset the source belongs to — a local .dataset.yaml path or a cloud dataset id
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
 
 .TP Examples:
 
 Examples:
-  postman dataset source remove ./users.dataset.yaml source_people_1
-  postman dataset source remove ./users.dataset.yaml d3e67bc9\-f9a3\-43b5\-b894\-d00f1791258c
+  postman dataset source remove \-d ./users.dataset.yaml source_people_1
+  postman dataset source remove \-d ./users.dataset.yaml d3e67bc9\-f9a3\-43b5\-b894\-d00f1791258c
+  postman dataset source remove \-d 14e30f6c\-1234\-1234\-1234\-cafef00dc0de source_people_1
 
 
 
@@ -2967,10 +3053,13 @@ Examples:
 [BETA] Update fields on an existing datasource. Only the flags you provide are changed.
 
 .B Usage:
-[options] <pathOrId> <sourceNameOrId>
+[options] <sourceNameOrId>
 
 .B Options:
 .TP
+.B \-d, \-\-dataset <datasetPathOrId>
+Dataset the source belongs to — a local .dataset.yaml path or a cloud dataset id
+.TP
 .B \-n, \-\-name <name>
 Rename the source
 .TP
@@ -2999,7 +3088,7 @@ Update DB port
 Update DB user (warning: stored as plaintext in the YAML).
 .TP
 .B \-\-password <password>
-Update DB password (warning: stored as plaintext in the YAML).
+Update DB password. WARNING: passing it here exposes it in `ps` output and shell history, and it is stored as plaintext in the dataset YAML (local) or sent in the request body (cloud). Prefer a restricted DB user; secure input (prompt / stdin / env) is planned.
 .TP
 .B \-\-database <db>
 Update DB database name
@@ -3009,6 +3098,9 @@ Update DB table name
 .TP
 .B \-\-slug <slug>
 Update slug
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
 
 .SS "dataset view"
 [BETA] Inspect and manage saved views on a dataset.
@@ -3019,35 +3111,42 @@ Update slug
 .B Subcommands:
 .TP
 .B dataset view list
-[BETA] List the saved views defined on a dataset.
+[BETA] List the saved views defined on a dataset (local YAML path or cloud id).
 .TP
 .B dataset view run
 [BETA] Execute a saved view against a dataset and print the rows.
 .TP
 .B dataset view create
-[BETA] Add a saved view to a dataset.
+[BETA] Add a saved view to a dataset (local YAML path or cloud id).
 .TP
 .B dataset view delete
-[BETA] Remove a saved view from a dataset.
+[BETA] Remove a saved view from a dataset (local YAML path or cloud id).
 .TP
 .B dataset view update
-[BETA] Update name and/or query on an existing view.
+[BETA] Update name and/or query on an existing view (local YAML path or cloud id).
 
 .SS "dataset view list"
-[BETA] List the saved views defined on a dataset.
+[BETA] List the saved views defined on a dataset (local YAML path or cloud id).
 
 .B Usage:
-[options] <path>
+[options]
 
 .B Options:
 .TP
+.B \-d, \-\-dataset <datasetPathOrId>
+Dataset whose views to list — a local .dataset.yaml path or a cloud dataset id
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
+.TP
 .B \-\-json
 Output views as JSON instead of a table
 
 .TP Examples:
 
 Examples:
-  postman dataset view list ./postman/datasets/users/users.dataset.yaml
+  postman dataset view list \-d ./postman/datasets/users/users.dataset.yaml
+  postman dataset view list \-d 14e30f6c\-1234\-1234\-1234\-cafef00dc0de
 
 
 
@@ -3055,80 +3154,111 @@ Examples:
 [BETA] Execute a saved view against a dataset and print the rows.
 
 .B Usage:
-[options] <path> <viewNameOrId>
+[options] <viewNameOrId>
 
 .B Options:
 .TP
+.B \-d, \-\-dataset <datasetPathOrId>
+Dataset the view belongs to — a local .dataset.yaml path or a cloud dataset id
+.TP
 .B \-p, \-\-param <value...>
 Positional parameter values for $1, $2, ... bindings; repeatable
 .TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
+.TP
 .B \-\-json
 Output rows as JSON instead of a table
 
 .TP Examples:
 
 Examples:
-  postman dataset view run ./users.dataset.yaml "Active Users"
-  postman dataset view run ./users.dataset.yaml ea748a6a\-ed3c\-496d\-b91e\-6ccc8e4d0e9d
+  postman dataset view run "Active Users" \-d ./users.dataset.yaml
+  postman dataset view run ea748a6a\-ed3c\-496d\-b91e\-6ccc8e4d0e9d \-d ./users.dataset.yaml
+  postman dataset view run "Active Users" \-d 14e30f6c\-1234\-1234\-1234\-cafef00dc0de
 
 
 
 .SS "dataset view create"
-[BETA] Add a saved view to a dataset.
+[BETA] Add a saved view to a dataset (local YAML path or cloud id).
 
 .B Usage:
-[options] <path>
+[options]
 
 .B Options:
 .TP
+.B \-d, \-\-dataset <datasetPathOrId>
+Dataset to add the view to — a local .dataset.yaml path or a cloud dataset id
+.TP
 .B \-n, \-\-name <name>
 View name
 .TP
 .B \-q, \-\-query <sql>
 SQL query the view executes
 .TP
-.B \-\-id <uuid>
-Override the generated view id
+.B \-\-view\-id <uuid>
+Override the generated view id (local only; cloud assigns its own)
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
 
 .TP Examples:
 
 Examples:
-  postman dataset view create ./users.dataset.yaml \e
+  postman dataset view create \-d ./users.dataset.yaml \e
     \-n "Active Users" \-q "SELECT * FROM source_users WHERE active = true"
+  postman dataset view create \-d 14e30f6c\-1234\-1234\-1234\-cafef00dc0de \e
+    \-n "Active Users" \-q "SELECT * FROM users WHERE active = true"
 
 
 
 .SS "dataset view delete"
-[BETA] Remove a saved view from a dataset.
+[BETA] Remove a saved view from a dataset (local YAML path or cloud id).
 
 .B Usage:
-[options] <path> <viewNameOrId>
+[options] <viewNameOrId>
+
+.B Options:
+.TP
+.B \-d, \-\-dataset <datasetPathOrId>
+Dataset the view belongs to — a local .dataset.yaml path or a cloud dataset id
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
 
 .TP Examples:
 
 Examples:
-  postman dataset view delete ./users.dataset.yaml "Active Users"
+  postman dataset view delete \-d ./users.dataset.yaml "Active Users"
+  postman dataset view delete \-d 14e30f6c\-1234\-1234\-1234\-cafef00dc0de "Active Users"
 
 
 
 .SS "dataset view update"
-[BETA] Update name and/or query on an existing view.
+[BETA] Update name and/or query on an existing view (local YAML path or cloud id).
 
 .B Usage:
-[options] <path> <viewNameOrId>
+[options] <viewNameOrId>
 
 .B Options:
 .TP
+.B \-d, \-\-dataset <datasetPathOrId>
+Dataset the view belongs to — a local .dataset.yaml path or a cloud dataset id
+.TP
 .B \-n, \-\-name <name>
 New view name
 .TP
 .B \-q, \-\-query <sql>
 New SQL query
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
 
 .TP Examples:
 
 Examples:
-  postman dataset view update ./users.dataset.yaml "Active Users" \-q "SELECT ..."
+  postman dataset view update "Active Users" \-d ./users.dataset.yaml \-q "SELECT ..."
+  postman dataset view update "Active Users" \-d 14e30f6c\-1234\-1234\-1234\-cafef00dc0de \-q "SELECT ..."
 
 
 

package/package.json

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