postman-cli 1.55.0 → 1.56.0

package/man/postman.1

@@ -1,4 +1,4 @@
-.TH POSTMAN 1 "2026-09-07" "v1.55.0" "Postman CLI Manual"
+.TH POSTMAN 1 "2026-09-08" "v1.56.0" "Postman CLI Manual"
 .SH NAME
 postman \- Command\-line companion utility for Postman
 .SH SYNOPSIS
@@ -66,8 +66,8 @@ Emit machine\-readable output for agents
 .B \-\-dry\-run
 Report what would happen without writing anything
 .TP
-.B \-\-no\-seed
-Do not derive a spec from source
+.B \-\-no\-fetch
+Use the skills bundled with this CLI instead of fetching the latest
 .TP
 .B \-\-spec <path>
 Which spec is authoritative, when more than one could be
@@ -83,7 +83,9 @@ Send init analytics to Postman (requires login)
 
 .TP Examples:
 
-Runs entirely locally: no authentication, no network, safe in CI.
+No authentication, and safe in CI. Fetches the latest skills over HTTPS,
+falling back to the copy bundled with this CLI if that is unreachable \-
+so it still works offline. \-\-no\-fetch skips the attempt.
 
 Not the same as `postman app init`, which writes a postman.config.cjs
 for test\-traffic capture.
@@ -111,6 +113,93 @@ Examples:
   $ postman init \-\-visibility personal
 
 
+.SS "skills"
+Check and update the agent skills in this repository.
+
+.B Usage:
+[options] [command]
+
+.TP Examples:
+
+Skills are written into postman/skills/ by `postman init` and committed,
+so they go stale for everyone who clones the repository. `status` says
+whether that has happened; `update` fixes it.
+
+The Claude Code plugin delivers the same skills separately \- refresh that
+with `claude plugin update postman`.
+
+
+.B Subcommands:
+.TP
+.B skills status
+Report whether this repository's skills are up to date.
+.TP
+.B skills update
+Fetch the latest skills into this repository.
+
+.SS "skills status"
+Report whether this repository's skills are up to date.
+
+.B Usage:
+[options] [path]
+
+.B Options:
+.TP
+.B \-\-json
+Emit machine\-readable output for agents
+.TP
+.B \-\-strict
+Exit non\-zero when the skills are not current
+
+.TP Examples:
+
+Makes one unauthenticated request. With a recorded ETag the origin
+answers 304 with an empty body, so this is cheap enough to run often.
+
+Exit codes:
+  0  the check completed \- read the state from the output
+  1  the skills repository could not be reached
+  3  not current, and \-\-strict was passed
+
+States:
+  current   matches what is published
+  behind    a newer version exists \- run `postman skills update`
+  modified  edited locally; update needs \-\-force
+  unknown   written before init recorded hashes, so not comparable
+
+Set POSTMAN_SKILLS_URL to check against a different origin.
+
+
+.SS "skills update"
+Fetch the latest skills into this repository.
+
+.B Usage:
+[options] [path]
+
+.B Options:
+.TP
+.B \-\-json
+Emit machine\-readable output for agents
+.TP
+.B \-\-dry\-run
+Report what would change without writing anything
+.TP
+.B \-\-force
+Overwrite skill files that were edited locally
+
+.TP Examples:
+
+Writes only the skills. Unlike `postman init` it creates no directories,
+touches no resources.yaml and never talks to a workspace.
+
+Exit codes:
+  0  up to date, or updated
+  1  the skills repository could not be reached, so there is nothing newer
+  4  refused: a skill file was edited locally \- re\-run with \-\-force
+
+Set POSTMAN_SKILLS_URL to update from a different origin.
+
+
 .SS "collection"
 Run and test your Postman collections directly from the command line.
 
@@ -904,6 +993,10 @@ Pass condition in format: function(metric, value).
 Functions: less_than, greater_than, less_than_eq, greater_than_eq. 
 Metrics: avg, p90, p95, p99, error_rate, rps. 
 Example: less_than(p95, 500) or less_than(error_rate, 5)
+.TP
+.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 Examples:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "postman-cli",
-  "version": "1.55.0",
+  "version": "1.56.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.55.0",
-    "@postman/pm-bin-macos-x64": "1.55.0",
-    "@postman/pm-bin-linux-x64": "1.55.0",
-    "@postman/pm-bin-linux-arm64": "1.55.0",
-    "@postman/pm-bin-windows-x64": "1.55.0"
+    "@postman/pm-bin-macos-arm64": "1.56.0",
+    "@postman/pm-bin-macos-x64": "1.56.0",
+    "@postman/pm-bin-linux-x64": "1.56.0",
+    "@postman/pm-bin-linux-arm64": "1.56.0",
+    "@postman/pm-bin-windows-x64": "1.56.0"
   }
 }