postman-cli 1.51.0 → 1.53.0

package/man/postman.1

@@ -1,4 +1,4 @@
-.TH POSTMAN 1 "2026-08-27" "v1.51.0" "Postman CLI Manual"
+.TH POSTMAN 1 "2026-09-02" "v1.53.0" "Postman CLI Manual"
 .SH NAME
 postman \- Command\-line companion utility for Postman
 .SH SYNOPSIS
@@ -269,14 +269,22 @@ Start a mock server from manifest (.json, .yaml or .yml) file
 .B \-\-port <port>
 Port for the \-\-mock server; pass "auto" for an OS\-assigned ephemeral port (default: configured port, falls back to an ephemeral one if busy). Only valid with \-\-mock.
 .TP
+.B \-\-use\-mock <mapping>
+Redirect requests for a URL or {{variable}} to a mock during the run. Format: "<url> mock|mock\-server:<path|id> [scenario]". Repeat the flag to redirect multiple URLs (one \-\-use\-mock per mock). Use "mock:<path>" for a local mock manifest (.json/.yaml/.yml), "mock:<id>" for a local mock by id (fetched from the cloud then run locally), or "mock\-server:<id>" to redirect to a deployed mock server's URL. Id\-based references require `postman login` (or \-\-postman\-api\-key). The optional third field selects a scenario (defaults to "default"). (default: )
+.TP
 .B \-\-simulate <path>
 Start mock servers with fault\-injection scenarios from a .sim.yaml file
 .TP
 .B \-\-report\-events
-Send run results and analytics to Postman
+Upload results for git\-native v3 collection runs. Analytics are sent by default
+.TP
+.B \-\-no\-report\-events
+Do not send analytics to Postman
 
 .TP Examples:
 Eg. postman collection run 123456\-45159473\-1e45\-1f34\-5678\-1234567890ab
+    postman collection run <id> \-\-use\-mock "{{baseurl}} mock:./mock/config.yaml delay"
+    postman collection run <id> \-\-use\-mock "{{baseurl}} mock:./a.yaml" \-\-use\-mock "api.com mock\-server:9d8e7f6a"
 
 
 .SS "environment"
@@ -469,7 +477,10 @@ Enable the metrics server for health checks
 Port for the metrics server (default: 9090)
 .TP
 .B \-\-report\-events
-Send run events and analytics to Postman
+Accepted for compatibility; analytics are sent by default
+.TP
+.B \-\-no\-report\-events
+Do not send analytics to Postman
 
 .SS "spec"
 Lint and validate Specifications from the command line
@@ -506,7 +517,10 @@ Output format for the results. [choices: "json", "csv"]
 The workspace ID to use for fetching governance rulesets.
 .TP
 .B \-\-report\-events
-Send lint results and analytics to Postman
+Accepted for compatibility; analytics are sent by default
+.TP
+.B \-\-no\-report\-events
+Do not send analytics to Postman
 
 .SS "spec ai\-readiness"
 Score an OpenAPI specification for AI readiness by ID or local file path.
@@ -647,7 +661,10 @@ Push strategy. "force\-sync": mirror the whole workspace — also DELETE cloud e
 Show detailed logging
 .TP
 .B \-\-report\-events
-Send workspace push events to Postman
+Accepted for compatibility; analytics are sent by default
+.TP
+.B \-\-no\-report\-events
+Do not send analytics to Postman
 
 .SS "workspace lint"
 Lint the current local Postman workspace: its configuration (.postman/resources.yaml) plus every discovered entity. Use \-\-meta to lint only the configuration.
@@ -750,6 +767,12 @@ Specify an Id to a Postman Environment
 .B \-g, \-\-globals <id>
 Specify an Id to a Postman Globals
 .TP
+.B \-\-setup\-collection <id>
+Collection UID to run before the Postman Cloud performance test
+.TP
+.B \-\-teardown\-collection <id>
+Collection UID to run after the Postman Cloud performance test
+.TP
 .B \-\-vu\-count <count>
 Number of virtual users (default: 20)
 .TP
@@ -788,6 +811,7 @@ Example: less_than(p95, 500) or less_than(error_rate, 5)
 Examples:
   postman performance run 123456\-45159473\-1e45\-1f34\-5678\-1234567890ab \-\-vu\-count 50 \-\-duration 15
   postman performance run 123456\-45159473\-1e45\-1f34\-5678\-1234567890ab \-\-pass\-if "less_than(p95, 500)"
+  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
 
 
 .SS "flows"
@@ -1005,6 +1029,12 @@ Specify whether or not to override the default exit code for the current run
 .B \-\-workspace <workspaceId>
 Workspace ID required for flows that contain connector blocks. Find it in the Postman app URL: https://postman.com/workspace/<workspaceId>
 .TP
+.B \-\-report\-events
+Accepted for compatibility; analytics are sent by default
+.TP
+.B \-\-no\-report\-events
+Do not send analytics to Postman
+.TP
 .B \-\-verbose
 Verbose output
 .TP
@@ -1209,6 +1239,12 @@ suppress all output except response body. Useful for piping to other commands.
 .TP
 .B \-\-debug
 Debug mode: show detailed execution information including retry attempts, redirects, and timing breakdowns.
+.TP
+.B \-\-report\-events
+Accepted for compatibility; analytics are sent by default
+.TP
+.B \-\-no\-report\-events
+Do not send analytics to Postman
 
 .TP Examples:
 
@@ -1820,7 +1856,7 @@ Examples:
 
 
 .SS "mock"
-Run and manage local Postman mock servers.
+Run and manage Postman mocks, locally and in the cloud.
 
 .B Usage:
 [options] [command]
@@ -1828,22 +1864,28 @@ Run and manage local Postman mock servers.
 .B Subcommands:
 .TP
 .B mock generate
-Generate a local, runnable mock from a Postman collection (v2.0/v2.1/v3 file, or a git\-native v3 collection directory) or an OpenAPI 3.0/3.1 spec file. The source type is auto\-detected. Omit the source to scaffold a sample mock with a GET /health endpoint.
+Generate a runnable mock from a Postman collection (v2.0/v2.1/v3 file, or a git\-native v3 collection directory) or an OpenAPI 3.0/3.1 spec file. The source type is auto\-detected. Omit the source to scaffold a sample mock with a GET /health endpoint. Writes a local mock by default, or a cloud mock with \-\-workspace.
 .TP
 .B mock run
-Start a local mock server given a manifest file (JSON or YAML), a mock directory (postman/mocks/<slug>), or a .js handler.
+Start a local mock server from a cloud mock id (fetched and run locally), a manifest file (JSON or YAML), a mock directory (postman/mocks/<slug>), or a .js handler.
+.TP
+.B mock deploy
+Deploy a cloud mock into a mock server.
 .TP
 .B mock get
-Show a local mock's details and run status.
+Show a mock's details: a cloud mock by id, or a local mock by path.
 .TP
 .B mock list
-List local mocks found under a directory.
+List a workspace's cloud mocks, or (with a path) local mocks under a directory.
+.TP
+.B mock log
+Browse a deployed mock server's request/response logs by its id (see `mock get`).
 .TP
 .B mock delete
-Permanently remove a local mock artifact.
+Permanently remove a mock: a cloud mock by id, or a local mock artifact by path.
 
 .SS "mock generate"
-Generate a local, runnable mock from a Postman collection (v2.0/v2.1/v3 file, or a git\-native v3 collection directory) or an OpenAPI 3.0/3.1 spec file. The source type is auto\-detected. Omit the source to scaffold a sample mock with a GET /health endpoint.
+Generate a runnable mock from a Postman collection (v2.0/v2.1/v3 file, or a git\-native v3 collection directory) or an OpenAPI 3.0/3.1 spec file. The source type is auto\-detected. Omit the source to scaffold a sample mock with a GET /health endpoint. Writes a local mock by default, or a cloud mock with \-\-workspace.
 
 .B Usage:
 [sourcePath] [options]
@@ -1865,6 +1907,12 @@ Overwrite the config.yaml/default.js in the output directory if it already exist
 .B \-u, \-\-update <mockPath>
 Update an existing mock in place from the source: path to its config.yaml (or the directory containing it). Regenerates the default scenario handler and preserves the existing name/port/scenarios. Cannot be combined with \-\-output.
 .TP
+.B \-w, \-\-workspace <id>
+Create a cloud mock in this Postman workspace instead of a local mock. Cannot be combined with \-\-output/\-\-force/\-\-update.
+.TP
+.B \-\-api\-key <key>
+Postman API key for \-\-workspace (defaults to the `postman login` session)
+.TP
 .B \-x, \-\-suppress\-exit\-code
 Always exit with code 0, even on failure
 
@@ -1875,13 +1923,14 @@ Eg. postman mock generate ./my\-collection.json
     postman mock generate \-\-name "My Mock" \-\-port 4010      # sample mock, custom port
     postman mock generate ./openapi.yaml \-\-output ./postman/mocks/api \-\-port 4010
     postman mock generate ./my\-collection.json \-\-update ./postman/mocks/orders
+    postman mock generate ./my\-collection.json \-w 12345678\-90ab\-cdef\-1234\-567890abcdef   # cloud mock
 
 
 .SS "mock run"
-Start a local mock server given a manifest file (JSON or YAML), a mock directory (postman/mocks/<slug>), or a .js handler.
+Start a local mock server from a cloud mock id (fetched and run locally), a manifest file (JSON or YAML), a mock directory (postman/mocks/<slug>), or a .js handler.
 
 .B Usage:
-<pathOrDir>
+<mockIdOrPath>
 
 .B Options:
 .TP
@@ -1893,9 +1942,13 @@ Path to a globals file (JSON or YAML) for pm.globals
 .TP
 .B \-p, \-\-port <port>
 Mock server port, or "auto" for an ephemeral one (default: configured port, falls back to an ephemeral one if busy).
+.TP
+.B \-\-api\-key <key>
+Postman API key for cloud mock ids (defaults to the `postman login` session)
 
 .TP Examples:
-Eg. postman mock run ./postman/mocks/orders            # a mock directory
+Eg. postman mock run 12345678\-90ab\-cdef\-1234\-567890abcdef  # cloud mock by id
+    postman mock run ./postman/mocks/orders            # a mock directory
     postman mock run ./postman/mock\-manifest.json
     postman mock run ./postman/mock\-manifest.yaml
     postman mock run ./manifest.json \-\-environment ./postman/environments/dev.yaml
@@ -1903,55 +1956,148 @@ Eg. postman mock run ./postman/mocks/orders            # a mock directory
     postman mock run ./manifest.yaml \-\-port 4600        # exact port, errors if busy
 
 
+.SS "mock deploy"
+Deploy a cloud mock into a mock server.
+
+.B Usage:
+<mockId> [options]
+
+.B Options:
+.TP
+.B \-w, \-\-workspace <id>
+Workspace that will own the mock server (defaults to the workspace linked in .postman/resources.yaml)
+.TP
+.B \-n, \-\-name <name>
+Display name for the mock server (prompts when omitted)
+.TP
+.B \-s, \-\-slug <slug>
+Slug for the deploy URL (prompts when omitted)
+.TP
+.B \-\-public
+Deploy as a public mock (default is private; requires an x\-api\-key header)
+.TP
+.B \-\-auto\-deploy
+Re\-deploy the mock automatically whenever it changes (default off)
+.TP
+.B \-y, \-\-yes
+Accept defaults and skip all prompts (private, no auto\-deploy)
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
+
+.TP Examples:
+
+Eg. postman mock deploy 12345678\-90ab\-cdef\-1234\-567890abcdef                 # interactive prompts
+    postman mock deploy 12345678\-90ab\-cdef\-1234\-567890abcdef \-\-slug my\-mock \-\-public
+    postman mock deploy 12345678\-90ab\-cdef\-1234\-567890abcdef \-n "My Mock" \-s my\-mock \-\-auto\-deploy
+    postman mock deploy 12345678\-90ab\-cdef\-1234\-567890abcdef \-s my\-mock \-y   # non\-interactive
+
+
 .SS "mock get"
-Show a local mock's details and run status.
+Show a mock's details: a cloud mock by id, or a local mock by path.
 
 .B Usage:
-<pathOrDir> [options]
+<mockIdOrPath> [options]
 
 .B Options:
 .TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
+.TP
 .B \-\-json
 Output the mock details as JSON instead of a table
 
 .TP Examples:
 
-Eg. postman mock get ./postman/mocks/orders
+Eg. postman mock get 12345678\-90ab\-cdef\-1234\-567890abcdef     # cloud mock by id
+    postman mock get ./postman/mocks/orders                   # local mock by path
     postman mock get ./postman/mocks/orders \-\-json
 
 
 .SS "mock list"
-List local mocks found under a directory.
+List a workspace's cloud mocks, or (with a path) local mocks under a directory.
 
 .B Usage:
 [pathOrDir] [options]
 
 .B Options:
 .TP
+.B \-w, \-\-workspace <id>
+Workspace whose cloud mocks to list (defaults to the workspace linked in .postman/resources.yaml)
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
+.TP
 .B \-\-json
 Output the mock list as JSON instead of a table
 
 .TP Examples:
 
-Eg. postman mock list
-    postman mock list ./postman/mocks
+Eg. postman mock list                                                 # linked workspace (cloud)
+    postman mock list \-w 12345678\-90ab\-cdef\-1234\-567890abcdef        # explicit workspace (cloud)
+    postman mock list ./postman/mocks                                # local mocks under a dir
     postman mock list ./postman/mocks \-\-json
 
 
+.SS "mock log"
+Browse a deployed mock server's request/response logs by its id (see `mock get`).
+
+.B Usage:
+<mockServerId> [options]
+
+.B Options:
+.TP
+.B \-\-limit <n>
+Maximum number of log entries to show (default 50 for \-\-json/non\-interactive output)
+.TP
+.B \-\-method <method>
+Filter by HTTP method (e.g. GET, POST)
+.TP
+.B \-\-status <code|range>
+Filter by response status (e.g. 404 or 5xx)
+.TP
+.B \-\-path <pattern>
+Filter by request path (supports * and ? wildcards)
+.TP
+.B \-\-since <duration>
+Show logs from this long ago onward (e.g. 2h = the last 2 hours)
+.TP
+.B \-\-until <duration>
+Stop this long ago (e.g. 30m = exclude the most recent 30 minutes)
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
+.TP
+.B \-\-json
+Output logs as JSON instead of the interactive pager
+
+.TP Examples:
+
+Eg. postman mock log 12345678\-90ab\-cdef\-1234\-567890abcdef            # interactive pager
+    postman mock log 12345678\-90ab\-cdef\-1234\-567890abcdef \-\-json     # outputs in JSON
+    postman mock log <mockServerId> \-\-method GET \-\-path '/users/*'
+    postman mock log <mockServerId> \-\-status 5xx \-\-limit 50
+    postman mock log <mockServerId> \-\-since 7h \-\-until 2h            # between 7h and 2h ago
+
+
 .SS "mock delete"
-Permanently remove a local mock artifact.
+Permanently remove a mock: a cloud mock by id, or a local mock artifact by path.
 
 .B Usage:
-<pathOrDir> [options]
+<mockIdOrPath> [options]
 
 .B Options:
 .TP
 .B \-y, \-\-yes
 Skip the confirmation prompt
+.TP
+.B \-\-api\-key <key>
+Postman API key for cloud mock ids (defaults to the `postman login` session)
 
 .TP Examples:
 
-Eg. postman mock delete ./postman/mocks/orders
+Eg. postman mock delete 12345678\-90ab\-cdef\-1234\-567890abcdef   # cloud mock by id
+    postman mock delete ./postman/mocks/orders                 # local mock by path
     postman mock delete ./postman/mocks/orders \-\-yes
     postman mock delete ./postman/mocks/orders/config.yaml \-\-yes
 
@@ -2056,8 +2202,11 @@ Overwrite the output directory if it exists and is not empty (used with \-\-capt
 .B \-\-save\-events\-local
 Write analytics events to pm\-results/test\-events\-debug.ndjson instead of sending to Postman
 .TP
-.B \-\-report\-events
-Send application test run results and analytics to Postman
+.B \-\-report\-events [boolean]
+Send application test run results to Postman (default: true)
+.TP
+.B \-\-no\-report\-events
+Do not send run results or analytics to Postman
 .TP
 .B \-\-verbose
 Show detailed per\-request matching, sandbox errors, and debug information
@@ -2073,7 +2222,8 @@ or via \-\-target\-collection/\-\-target\-environment flags. CLI flags override
 Use \-\-capture\-only to skip tests and export captured traffic
 as a V3 Postman collection organised by host.
 
-Use \-\-report\-events to send run results to Postman. Analytics are also sent automatically when running in CI.
+Run results are sent to Postman automatically after analysis.
+Use \-\-report\-events=false (or \-\-report\-events false) to skip uploading run results.
 
 Examples:
   postman application test \-\-command "npx playwright test"
@@ -3175,7 +3325,7 @@ Examples:
 
 
 .SS "dataset"
-[BETA] Work with Postman datasets in local YAML files or the cloud.
+Work with Postman datasets in local YAML files or the cloud.
 
 .B Usage:
 [options] [command]
@@ -3192,28 +3342,28 @@ Targeting:
 .B Subcommands:
 .TP
 .B dataset list
-[BETA] List local dataset YAMLs under a path, or (no path) a workspace's cloud datasets.
+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 (local YAML path or cloud id).
+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 (local YAML path or cloud id).
+Run an ad\-hoc SQL query against a dataset (local YAML path or cloud id).
 .TP
 .B dataset create
-[BETA] Scaffold a new .dataset.yaml at <path>, or (no path, with \-w) create a cloud dataset.
+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: a local .dataset.yaml or a cloud dataset id.
+Permanently remove a dataset: a local .dataset.yaml or a cloud dataset id.
 .TP
 .B dataset source
-[BETA] Inspect and manage a dataset's datasources.
+Inspect and manage a dataset's datasources.
 .TP
 .B dataset view
-[BETA] Inspect and manage saved views on a dataset.
+Inspect and manage saved views on a dataset.
 
 .SS "dataset list"
-[BETA] List local dataset YAMLs under a path, or (no path) a workspace's cloud datasets.
+List local dataset YAMLs under a path, or (no path) a workspace's cloud datasets.
 
 .B Usage:
 [options] [pathOrDir]
@@ -3239,7 +3389,7 @@ Examples:
 
 
 .SS "dataset get"
-[BETA] Print a dataset's metadata and structure summary (local YAML path or cloud id).
+Print a dataset's metadata and structure summary (local YAML path or cloud id).
 
 .B Usage:
 [options] <datasetPathOrId>
@@ -3264,7 +3414,7 @@ Examples:
 
 
 .SS "dataset query"
-[BETA] Run an ad\-hoc SQL query against a dataset (local YAML path or cloud id).
+Run an ad\-hoc SQL query against a dataset (local YAML path or cloud id).
 
 .B Usage:
 [options] <datasetPathOrId>
@@ -3297,7 +3447,7 @@ Examples:
 
 
 .SS "dataset create"
-[BETA] Scaffold a new .dataset.yaml at <path>, or (no path, with \-w) create a cloud dataset.
+Scaffold a new .dataset.yaml at <path>, or (no path, with \-w) create a cloud dataset.
 
 .B Usage:
 [options] [path]
@@ -3331,7 +3481,7 @@ Examples:
 
 
 .SS "dataset delete"
-[BETA] Permanently remove a dataset: a local .dataset.yaml or a cloud dataset id.
+Permanently remove a dataset: a local .dataset.yaml or a cloud dataset id.
 
 .B Usage:
 [options] <datasetPathOrId>
@@ -3361,7 +3511,7 @@ Local resource cleanup:
 
 
 .SS "dataset source"
-[BETA] Inspect and manage a dataset's datasources.
+Inspect and manage a dataset's datasources.
 
 .B Usage:
 [options] [command]
@@ -3369,19 +3519,19 @@ Local resource cleanup:
 .B Subcommands:
 .TP
 .B dataset source list
-[BETA] List the datasources defined on a dataset (local YAML path or cloud id).
+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.
+Add a datasource to a dataset.
 .TP
 .B dataset source remove
-[BETA] Remove a datasource from a dataset (local YAML path or cloud id).
+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.
+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 (local YAML path or cloud id).
+List the datasources defined on a dataset (local YAML path or cloud id).
 
 .B Usage:
 [options]
@@ -3406,7 +3556,7 @@ Examples:
 
 
 .SS "dataset source add"
-[BETA] Add a datasource to a dataset.
+Add a datasource to a dataset.
 
 .B Usage:
 [options] [datasetPathOrId]
@@ -3520,7 +3670,7 @@ Execution:
 
 
 .SS "dataset source remove"
-[BETA] Remove a datasource from a dataset (local YAML path or cloud id).
+Remove a datasource from a dataset (local YAML path or cloud id).
 
 .B Usage:
 [options] <sourceNameOrId>
@@ -3543,7 +3693,7 @@ Examples:
 
 
 .SS "dataset source update"
-[BETA] Update fields on an existing datasource. Only the flags you provide are changed.
+Update fields on an existing datasource. Only the flags you provide are changed.
 
 .B Usage:
 [options] <sourceNameOrId>
@@ -3642,7 +3792,7 @@ Examples:
 
 
 .SS "dataset view"
-[BETA] Inspect and manage saved views on a dataset.
+Inspect and manage saved views on a dataset.
 
 .B Usage:
 [options] [command]
@@ -3650,22 +3800,22 @@ Examples:
 .B Subcommands:
 .TP
 .B dataset view list
-[BETA] List the saved views defined on a dataset (local YAML path or cloud id).
+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.
+Execute a saved view against a dataset and print the rows.
 .TP
 .B dataset view create
-[BETA] Add a saved view to a dataset (local YAML path or cloud id).
+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 (local YAML path or cloud id).
+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 (local YAML path or cloud id).
+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 (local YAML path or cloud id).
+List the saved views defined on a dataset (local YAML path or cloud id).
 
 .B Usage:
 [options]
@@ -3690,7 +3840,7 @@ Examples:
 
 
 .SS "dataset view run"
-[BETA] Execute a saved view against a dataset and print the rows.
+Execute a saved view against a dataset and print the rows.
 
 .B Usage:
 [options] <viewNameOrId>
@@ -3724,7 +3874,7 @@ Examples:
 
 
 .SS "dataset view create"
-[BETA] Add a saved view to a dataset (local YAML path or cloud id).
+Add a saved view to a dataset (local YAML path or cloud id).
 
 .B Usage:
 [options]
@@ -3757,7 +3907,7 @@ Examples:
 
 
 .SS "dataset view delete"
-[BETA] Remove a saved view from a dataset (local YAML path or cloud id).
+Remove a saved view from a dataset (local YAML path or cloud id).
 
 .B Usage:
 [options] <viewNameOrId>
@@ -3779,7 +3929,7 @@ Examples:
 
 
 .SS "dataset view update"
-[BETA] Update name and/or query on an existing view (local YAML path or cloud id).
+Update name and/or query on an existing view (local YAML path or cloud id).
 
 .B Usage:
 [options] <viewNameOrId>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "postman-cli",
-  "version": "1.51.0",
+  "version": "1.53.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.51.0",
-    "@postman/pm-bin-macos-x64": "1.51.0",
-    "@postman/pm-bin-linux-x64": "1.51.0",
-    "@postman/pm-bin-linux-arm64": "1.51.0",
-    "@postman/pm-bin-windows-x64": "1.51.0"
+    "@postman/pm-bin-macos-arm64": "1.53.0",
+    "@postman/pm-bin-macos-x64": "1.53.0",
+    "@postman/pm-bin-linux-x64": "1.53.0",
+    "@postman/pm-bin-linux-arm64": "1.53.0",
+    "@postman/pm-bin-windows-x64": "1.53.0"
   }
 }