@sanity/runtime-cli 12.3.0 → 13.0.0

package/README.md

@@ -20,7 +20,7 @@ $ npm install -g @sanity/runtime-cli
 $ sanity-run COMMAND
 running command...
 $ sanity-run (--version)
-@sanity/runtime-cli/12.3.0 linux-x64 node-v24.11.1
+@sanity/runtime-cli/13.0.0 linux-x64 node-v24.12.0
 $ sanity-run --help [COMMAND]
 USAGE
   $ sanity-run COMMAND
@@ -44,13 +44,13 @@ USAGE
 * [`sanity-run functions env add NAME KEY VALUE`](#sanity-run-functions-env-add-name-key-value)
 * [`sanity-run functions env list NAME`](#sanity-run-functions-env-list-name)
 * [`sanity-run functions env remove NAME KEY`](#sanity-run-functions-env-remove-name-key)
-* [`sanity-run functions logs NAME`](#sanity-run-functions-logs-name)
-* [`sanity-run functions test NAME`](#sanity-run-functions-test-name)
+* [`sanity-run functions logs [NAME]`](#sanity-run-functions-logs-name)
+* [`sanity-run functions test [NAME]`](#sanity-run-functions-test-name)
 * [`sanity-run help [COMMAND]`](#sanity-run-help-command)
 
 ## `sanity-run blueprints add TYPE`
 
-Add a Resource to a Blueprint
+Add a function resource to a Blueprint
 
 ```
 USAGE
@@ -60,25 +60,31 @@ USAGE
     skip|npm|pnpm|yarn] [-i | ]
 
 ARGUMENTS
-  TYPE  (function) Type of Resource to add (e.g. function)
+  TYPE  (function) Type of resource to add (only "function" is supported)
 
 FLAGS
   -i, --install                Shortcut for --fn-installer npm
-  -n, --name=<value>           Name of the Resource to add
-      --example=<value>        Example to use for the Resource
-      --[no-]fn-helpers        Add helpers to the new Function
-      --fn-installer=<option>  How to install the @sanity/functions helpers
+  -n, --name=<value>           Name of the resource to add
+      --example=<value>        Example to use for the function resource. Discover examples at
+                               https://www.sanity.io/exchange/type=recipes/by=sanity
+      --[no-]fn-helpers        Add helpers to the new function
+      --fn-installer=<option>  Which package manager to use when installing the @sanity/functions helpers
                                <options: skip|npm|pnpm|yarn>
       --fn-type=<option>...    Document change event(s) that should trigger the function; you can specify multiple
                                events by specifying this flag multiple times
                                <options: document-create|document-delete|document-update|document-publish|media-library-
                                asset-create|media-library-asset-update|media-library-asset-delete>
       --javascript             Use JavaScript instead of TypeScript
-      --language=<option>      [default: ts] Language of the new Function
+      --language=<option>      [default: ts] Language of the new function
                                <options: ts|js>
 
 DESCRIPTION
-  Add a Resource to a Blueprint
+  Add a function resource to a Blueprint
+
+  Scaffolds a new Sanity Function in your Blueprint. Functions are serverless handlers triggered by document events
+  (create, update, delete, publish) or media library events.
+
+  After adding a function, use 'functions dev' to test locally, then 'blueprints deploy' to publish it.
 
 EXAMPLES
   $ sanity-run blueprints add function
@@ -92,11 +98,11 @@ EXAMPLES
   $ sanity-run blueprints add function --name my-function --fn-type document-create --fn-type document-update --lang js
 ```
 
-_See code: [src/commands/blueprints/add.ts](https://github.com/sanity-io/runtime-cli/blob/v12.3.0/src/commands/blueprints/add.ts)_
+_See code: [src/commands/blueprints/add.ts](https://github.com/sanity-io/runtime-cli/blob/v13.0.0/src/commands/blueprints/add.ts)_
 
 ## `sanity-run blueprints config`
 
-View or edit Blueprint configuration
+View or edit the local Blueprint configuration
 
 ```
 USAGE
@@ -104,12 +110,19 @@ USAGE
 
 FLAGS
   -e, --edit                     Modify the configuration interactively, or directly when combined with ID flags.
-      --organization-id=<value>  Directly set the Organization ID in the configuration. Requires --edit flag
-      --project-id=<value>       Directly set the Project ID in the configuration. Requires --edit flag
+      --organization-id=<value>  Directly set the organization ID in the configuration. Requires --edit flag
+      --project-id=<value>       Directly set the project ID in the configuration. Requires --edit flag
       --stack-id=<value>         Directly set the Stack ID in the configuration. Requires --edit flag
 
 DESCRIPTION
-  View or edit Blueprint configuration
+  View or edit the local Blueprint configuration
+
+  Manages the local Blueprint configuration, which links your Blueprint to a Sanity project and Stack.
+
+  Without flags, displays the current configuration. Use --edit to interactively modify settings, or combine --edit with
+  ID flags to update values directly (useful for scripting and automation).
+
+  If you need to switch your Blueprint to a different Stack, use --edit --stack-id.
 
 EXAMPLES
   $ sanity-run blueprints config
@@ -121,11 +134,11 @@ EXAMPLES
   $ sanity-run blueprints config --edit --project-id <projectId> --stack-id <stackId>
 ```
 
-_See code: [src/commands/blueprints/config.ts](https://github.com/sanity-io/runtime-cli/blob/v12.3.0/src/commands/blueprints/config.ts)_
+_See code: [src/commands/blueprints/config.ts](https://github.com/sanity-io/runtime-cli/blob/v13.0.0/src/commands/blueprints/config.ts)_
 
 ## `sanity-run blueprints deploy`
 
-Deploy a Blueprint
+Deploy the local Blueprint to the remote Stack
 
 ```
 USAGE
@@ -135,7 +148,15 @@ FLAGS
   --no-wait  Do not wait for Stack deployment to complete
 
 DESCRIPTION
-  Deploy a Blueprint
+  Deploy the local Blueprint to the remote Stack
+
+  Pushes your local Blueprint configuration to the remote Stack; provisioning, updating, or destroying resources as
+  needed. This is the primary command for applying infrastructure changes.
+
+  Before deploying, run 'blueprints plan' to preview changes. After deployment, use 'blueprints info' to verify Stack
+  status or 'blueprints logs' to monitor activity.
+
+  Use --no-wait to queue the deployment and return immediately without waiting for completion.
 
 EXAMPLES
   $ sanity-run blueprints deploy
@@ -143,11 +164,11 @@ EXAMPLES
   $ sanity-run blueprints deploy --no-wait
 ```
 
-_See code: [src/commands/blueprints/deploy.ts](https://github.com/sanity-io/runtime-cli/blob/v12.3.0/src/commands/blueprints/deploy.ts)_
+_See code: [src/commands/blueprints/deploy.ts](https://github.com/sanity-io/runtime-cli/blob/v13.0.0/src/commands/blueprints/deploy.ts)_
 
 ## `sanity-run blueprints destroy`
 
-Destroy a Blueprint Stack deployment and its resources (will not delete local files)
+Destroy the remote Stack deployment and its resources (will not delete local files)
 
 ```
 USAGE
@@ -162,7 +183,14 @@ FLAGS
   --stack-id=<value>         Stack ID to destroy (defaults to current Stack)
 
 DESCRIPTION
-  Destroy a Blueprint Stack deployment and its resources (will not delete local files)
+  Destroy the remote Stack deployment and its resources (will not delete local files)
+
+  Permanently removes the remote Stack and all its provisioned resources. Your local Blueprint files remain untouched,
+  allowing you to redeploy later with 'blueprints init' + 'blueprints deploy'.
+
+  This is a destructive operation. You will be prompted to confirm unless --force is specified.
+
+  Use this to clean up test environments or decommission a Stack you no longer need.
 
 EXAMPLES
   $ sanity-run blueprints destroy
@@ -170,40 +198,55 @@ EXAMPLES
   $ sanity-run blueprints destroy --stack-id <stackId> --project-id <projectId> --force --no-wait
 ```
 
-_See code: [src/commands/blueprints/destroy.ts](https://github.com/sanity-io/runtime-cli/blob/v12.3.0/src/commands/blueprints/destroy.ts)_
+_See code: [src/commands/blueprints/destroy.ts](https://github.com/sanity-io/runtime-cli/blob/v13.0.0/src/commands/blueprints/destroy.ts)_
 
 ## `sanity-run blueprints doctor`
 
-Diagnose potential issues with Blueprint configuration
+Diagnose potential issues with local Blueprint and remote Stack configuration
 
 ```
 USAGE
-  $ sanity-run blueprints doctor [--verbose] [--path <value>] [--fix]
+  $ sanity-run blueprints doctor [--json] [--path <value>] [--verbose] [--fix]
 
 FLAGS
   --fix           Interactively fix configuration issues
-  --path=<value>  Path to the Blueprint configuration file
-  --verbose       Provide detailed information about issues
+  --json          Format output as json.
+  --path=<value>  Path to the directory containing the Blueprint
+  --verbose       Verbose output
 
 DESCRIPTION
-  Diagnose potential issues with Blueprint configuration
+  Diagnose potential issues with local Blueprint and remote Stack configuration
+
+  Analyzes your local Blueprint and remote Stack configuration for common issues, such as missing authentication,
+  invalid project references, or misconfigured resources.
+
+  Run this command when encountering errors with other Blueprint commands. Use --fix to interactively resolve detected
+  issues.
 ```
 
-_See code: [src/commands/blueprints/doctor.ts](https://github.com/sanity-io/runtime-cli/blob/v12.3.0/src/commands/blueprints/doctor.ts)_
+_See code: [src/commands/blueprints/doctor.ts](https://github.com/sanity-io/runtime-cli/blob/v13.0.0/src/commands/blueprints/doctor.ts)_
 
 ## `sanity-run blueprints info`
 
-Show information about a Blueprint Stack deployment
+Show information about the local Blueprint's remote Stack deployment
 
 ```
 USAGE
   $ sanity-run blueprints info [--id <value>]
 
 FLAGS
-  --id=<value>  Stack ID to show info for (defaults to current Stack)
+  --id=<value>  Stack ID to show info for (defaults to the current Stack)
 
 DESCRIPTION
-  Show information about a Blueprint Stack deployment
+  Show information about the local Blueprint's remote Stack deployment
+
+  Displays the current state and metadata of your remote Stack deployment, including deployed resources, status, and
+  configuration.
+
+  Use this command to verify a deployment succeeded, check what resources are live, or confirm which Stack your local
+  Blueprint is connected to.
+
+  Run 'blueprints stacks' to see all available Stacks in your project or organization.
 
 EXAMPLES
   $ sanity-run blueprints info
@@ -211,33 +254,44 @@ EXAMPLES
   $ sanity-run blueprints info --id <stackId>
 ```
 
-_See code: [src/commands/blueprints/info.ts](https://github.com/sanity-io/runtime-cli/blob/v12.3.0/src/commands/blueprints/info.ts)_
+_See code: [src/commands/blueprints/info.ts](https://github.com/sanity-io/runtime-cli/blob/v13.0.0/src/commands/blueprints/info.ts)_
 
 ## `sanity-run blueprints init [DIR]`
 
-Initialize a new Blueprint Stack deployment
+Initialize a local Blueprint and optionally provision a remote Stack deployment
 
 ```
 USAGE
-  $ sanity-run blueprints init [DIR] [--dir <value>] [--example <value> | --blueprint-type json|js|ts | --stack-id
-    <value> | --stack-name <value>] [--project-id <value>] [--organization-id <value>] [--verbose]
+  $ sanity-run blueprints init [DIR] [--verbose] [--dir <value>] [--example <value> | --blueprint-type json|js|ts |
+    --stack-id <value> | --stack-name <value>] [--project-id <value>] [--organization-id <value>]
 
 ARGUMENTS
-  [DIR]  Directory to create the Blueprint in
+  [DIR]  Directory to create the local Blueprint in
 
 FLAGS
-  --blueprint-type=<option>  Blueprint manifest type to use for the Blueprint
+  --blueprint-type=<option>  Blueprint manifest type to use for the local Blueprint
                              <options: json|js|ts>
-  --dir=<value>              Directory to create the Blueprint in
-  --example=<value>          Example to use for the Blueprint
-  --organization-id=<value>  Sanity Organization ID to use for the Blueprint
-  --project-id=<value>       Sanity Project ID to use for the Blueprint
-  --stack-id=<value>         Existing Stack ID to use for the Blueprint
-  --stack-name=<value>       Name to use for a NEW Stack
+  --dir=<value>              Directory to create the local Blueprint in
+  --example=<value>          Example to use for the local Blueprint
+  --organization-id=<value>  Sanity organization ID used to scope local Blueprint and remote Stack
+  --project-id=<value>       Sanity project ID used to scope local Blueprint and remote Stack
+  --stack-id=<value>         Existing Stack ID used to scope local Blueprint
+  --stack-name=<value>       Name to use for a new Stack provisioned during initialization
   --verbose                  Verbose output
 
 DESCRIPTION
-  Initialize a new Blueprint Stack deployment
+  Initialize a local Blueprint and optionally provision a remote Stack deployment
+
+  A Blueprint is your local infrastructure-as-code configuration that defines Sanity resources (datasets, functions,
+  etc.). A Stack is the remote deployment target where your Blueprint is applied.
+  [NOTE: Currently, accounts are limited to three (3) Stacks per project scope.]
+
+  This is typically the first command you run in a new project. It creates a local Blueprint manifest file
+  (sanity.blueprint.ts, .js, or .json) and provisions a new remote Stack.
+  Additionally, a Blueprint configuration file is created in .sanity/ containing the scope and Stack IDs. This is
+  .gitignored by default.
+
+  After initialization, use 'blueprints plan' to preview changes, then 'blueprints deploy' to apply them.
 
 EXAMPLES
   $ sanity-run blueprints init
@@ -251,11 +305,11 @@ EXAMPLES
   $ sanity-run blueprints init --blueprint-type <json|js|ts> --stack-name <stackName>
 ```
 
-_See code: [src/commands/blueprints/init.ts](https://github.com/sanity-io/runtime-cli/blob/v12.3.0/src/commands/blueprints/init.ts)_
+_See code: [src/commands/blueprints/init.ts](https://github.com/sanity-io/runtime-cli/blob/v13.0.0/src/commands/blueprints/init.ts)_
 
 ## `sanity-run blueprints logs`
 
-Display logs for a Blueprint Stack deployment
+Display logs for the current Blueprint's Stack deployment
 
 ```
 USAGE
@@ -265,7 +319,13 @@ FLAGS
   -w, --watch  Watch for new Stack logs (streaming mode)
 
 DESCRIPTION
-  Display logs for a Blueprint Stack deployment
+  Display logs for the current Blueprint's Stack deployment
+
+  Retrieves Stack deployment logs, useful for debugging and monitoring deployment activity.
+
+  Use --watch (-w) to stream logs in real-time.
+
+  If you're not seeing expected logs, verify your Stack is deployed with 'blueprints info'.
 
 EXAMPLES
   $ sanity-run blueprints logs
@@ -273,39 +333,50 @@ EXAMPLES
   $ sanity-run blueprints logs --watch
 ```
 
-_See code: [src/commands/blueprints/logs.ts](https://github.com/sanity-io/runtime-cli/blob/v12.3.0/src/commands/blueprints/logs.ts)_
+_See code: [src/commands/blueprints/logs.ts](https://github.com/sanity-io/runtime-cli/blob/v13.0.0/src/commands/blueprints/logs.ts)_
 
 ## `sanity-run blueprints plan`
 
-Enumerate resources to be deployed - will not modify any resources
+Enumerate resources to be deployed to the remote Stack - will not modify any resources
 
 ```
 USAGE
   $ sanity-run blueprints plan
 
 DESCRIPTION
-  Enumerate resources to be deployed - will not modify any resources
+  Enumerate resources to be deployed to the remote Stack - will not modify any resources
+
+  Use this command to preview what changes will be applied to your remote Stack before deploying. This is a safe,
+  read-only operation—no resources are created, modified, or deleted.
+
+  Run 'blueprints plan' after making local changes to your Blueprint manifest to verify the expected diff. When ready,
+  run 'blueprints deploy' to apply changes.
 
 EXAMPLES
   $ sanity-run blueprints plan
 ```
 
-_See code: [src/commands/blueprints/plan.ts](https://github.com/sanity-io/runtime-cli/blob/v12.3.0/src/commands/blueprints/plan.ts)_
+_See code: [src/commands/blueprints/plan.ts](https://github.com/sanity-io/runtime-cli/blob/v13.0.0/src/commands/blueprints/plan.ts)_
 
 ## `sanity-run blueprints stacks`
 
-List all Blueprint Stacks
+List all remote Stack deployments (defaults to the current Blueprint's project scope)
 
 ```
 USAGE
   $ sanity-run blueprints stacks [--project-id <value> | --organization-id <value>]
 
 FLAGS
-  --organization-id=<value>  Organization ID to show stacks for
-  --project-id=<value>       Project ID to show stacks for
+  --organization-id=<value>  Organization ID to show Stack deployments for
+  --project-id=<value>       Project ID to show Stack deployments for
 
 DESCRIPTION
-  List all Blueprint Stacks
+  List all remote Stack deployments (defaults to the current Blueprint's project scope)
+
+  Shows all Stacks associated with a project or organization. By default, lists Stacks scoped to the local Blueprint.
+
+  Use this to discover existing Stacks you can scope a local Blueprint to (using 'blueprints config --edit'), or to
+  audit what's deployed across your project.
 
 EXAMPLES
   $ sanity-run blueprints stacks
@@ -315,7 +386,7 @@ EXAMPLES
   $ sanity-run blueprints stacks --organization-id <organizationId>
 ```
 
-_See code: [src/commands/blueprints/stacks.ts](https://github.com/sanity-io/runtime-cli/blob/v12.3.0/src/commands/blueprints/stacks.ts)_
+_See code: [src/commands/blueprints/stacks.ts](https://github.com/sanity-io/runtime-cli/blob/v13.0.0/src/commands/blueprints/stacks.ts)_
 
 ## `sanity-run functions add`
 
@@ -345,6 +416,13 @@ FLAGS
 DESCRIPTION
   Add a Function to your Blueprint
 
+  Scaffolds a new Function in the functions/ folder and templates a resource for your Blueprint manifest.
+
+  Functions are serverless handlers triggered by document events (create, update, delete, publish) or media library
+  events.
+
+  After adding, use 'functions dev' to test locally, then 'blueprints deploy' to publish.
+
 EXAMPLES
   $ sanity-run functions add
 
@@ -357,7 +435,7 @@ EXAMPLES
   $ sanity-run functions add --name my-function --type document-create --type document-update --lang js
 ```
 
-_See code: [src/commands/functions/add.ts](https://github.com/sanity-io/runtime-cli/blob/v12.3.0/src/commands/functions/add.ts)_
+_See code: [src/commands/functions/add.ts](https://github.com/sanity-io/runtime-cli/blob/v13.0.0/src/commands/functions/add.ts)_
 
 ## `sanity-run functions dev`
 
@@ -376,15 +454,26 @@ FLAGS
 DESCRIPTION
   Start the Sanity Function emulator
 
+  Runs a local, web-based development server to test your functions before deploying.
+
+  Open the emulator in your browser to interactively test your functions with the payload editor.
+
+  Optionally, set the host and port with the --host and --port flags. Function timeout can be configured with the
+  --timeout flag.
+
+  To invoke a function with the CLI, use 'functions test'.
+
 EXAMPLES
   $ sanity-run functions dev --host 127.0.0.1 --port 8974
+
+  $ sanity-run functions dev --timeout 60
 ```
 
-_See code: [src/commands/functions/dev.ts](https://github.com/sanity-io/runtime-cli/blob/v12.3.0/src/commands/functions/dev.ts)_
+_See code: [src/commands/functions/dev.ts](https://github.com/sanity-io/runtime-cli/blob/v13.0.0/src/commands/functions/dev.ts)_
 
 ## `sanity-run functions env add NAME KEY VALUE`
 
-Add or set the value of an environment variable for a Sanity function
+Add or set an environment variable for a deployed function
 
 ```
 USAGE
@@ -396,17 +485,22 @@ ARGUMENTS
   VALUE  The value of the environment variable
 
 DESCRIPTION
-  Add or set the value of an environment variable for a Sanity function
+  Add or set an environment variable for a deployed function
+
+  Sets an environment variable in a deployed Sanity Function. If the variable already exists, its value is updated.
+
+  Environment variables are useful for API keys, configuration values, and other secrets that shouldn't be hardcoded.
+  Changes take effect on the next function invocation.
 
 EXAMPLES
   $ sanity-run functions env add MyFunction API_URL https://api.example.com/
 ```
 
-_See code: [src/commands/functions/env/add.ts](https://github.com/sanity-io/runtime-cli/blob/v12.3.0/src/commands/functions/env/add.ts)_
+_See code: [src/commands/functions/env/add.ts](https://github.com/sanity-io/runtime-cli/blob/v13.0.0/src/commands/functions/env/add.ts)_
 
 ## `sanity-run functions env list NAME`
 
-List the environment variables for a Sanity function
+List environment variables for a deployed function
 
 ```
 USAGE
@@ -416,17 +510,21 @@ ARGUMENTS
   NAME  The name of the Sanity Function
 
 DESCRIPTION
-  List the environment variables for a Sanity function
+  List environment variables for a deployed function
+
+  Displays all environment variables (keys only) configured in a deployed Sanity Function.
+
+  Use 'functions env add' to set variables or 'functions env remove' to delete them.
 
 EXAMPLES
   $ sanity-run functions env list MyFunction
 ```
 
-_See code: [src/commands/functions/env/list.ts](https://github.com/sanity-io/runtime-cli/blob/v12.3.0/src/commands/functions/env/list.ts)_
+_See code: [src/commands/functions/env/list.ts](https://github.com/sanity-io/runtime-cli/blob/v13.0.0/src/commands/functions/env/list.ts)_
 
 ## `sanity-run functions env remove NAME KEY`
 
-Remove an environment variable for a Sanity function
+Remove an environment variable from a deployed function
 
 ```
 USAGE
@@ -437,24 +535,29 @@ ARGUMENTS
   KEY   The name of the environment variable
 
 DESCRIPTION
-  Remove an environment variable for a Sanity function
+  Remove an environment variable from a deployed function
+
+  Deletes an environment variable from a deployed Sanity Function. The change takes effect on the next function
+  invocation.
+
+  Use 'functions env list' to see current variables before removing.
 
 EXAMPLES
   $ sanity-run functions env remove MyFunction API_URL
 ```
 
-_See code: [src/commands/functions/env/remove.ts](https://github.com/sanity-io/runtime-cli/blob/v12.3.0/src/commands/functions/env/remove.ts)_
+_See code: [src/commands/functions/env/remove.ts](https://github.com/sanity-io/runtime-cli/blob/v13.0.0/src/commands/functions/env/remove.ts)_
 
-## `sanity-run functions logs NAME`
+## `sanity-run functions logs [NAME]`
 
 Retrieve or delete logs for a Sanity Function
 
 ```
 USAGE
-  $ sanity-run functions logs NAME [-u] [-f [-d | -l <value> | -j]] [-w]
+  $ sanity-run functions logs [NAME] [-u] [-f [-d | -l <value> | -j]] [-w]
 
 ARGUMENTS
-  NAME  The name of the Sanity Function
+  [NAME]  The name of the Sanity Function
 
 FLAGS
   -d, --delete         Delete all logs for the function
@@ -467,6 +570,11 @@ FLAGS
 DESCRIPTION
   Retrieve or delete logs for a Sanity Function
 
+  Fetches execution logs from a deployed function, useful for debugging production issues or monitoring activity.
+
+  Use --watch (-w) to stream logs in real-time. Use --delete to clear all logs for a function (requires confirmation
+  unless --force is specified).
+
 EXAMPLES
   $ sanity-run functions logs <name>
 
@@ -477,21 +585,21 @@ EXAMPLES
   $ sanity-run functions logs <name> --delete
 ```
 
-_See code: [src/commands/functions/logs.ts](https://github.com/sanity-io/runtime-cli/blob/v12.3.0/src/commands/functions/logs.ts)_
+_See code: [src/commands/functions/logs.ts](https://github.com/sanity-io/runtime-cli/blob/v13.0.0/src/commands/functions/logs.ts)_
 
-## `sanity-run functions test NAME`
+## `sanity-run functions test [NAME]`
 
 Invoke a local Sanity Function
 
 ```
 USAGE
-  $ sanity-run functions test NAME [--data-before <value> | [-d <value> | -f <value> | --document-id <value>] |  | 
+  $ sanity-run functions test [NAME] [--data-before <value> | [-d <value> | -f <value> | --document-id <value>] |  |
     | --file-before <value> | --file-after <value> | --document-id-before <value> | --document-id-after <value>]
     [--data-after <value> |  |  |  |  |  |  | ] [-e create|update|delete] [-t <value>] [-a <value>] [--organization-id
     <value>] [--with-user-token] [--media-library-id <value> | --project-id <value> | --dataset <value>]
 
 ARGUMENTS
-  NAME  The name of the Sanity Function
+  [NAME]  The name of the Sanity Function
 
 FLAGS
   -a, --api=<value>                 Sanity API Version to use
@@ -516,6 +624,12 @@ FLAGS
 DESCRIPTION
   Invoke a local Sanity Function
 
+  Executes a function locally with the provided payload, simulating how it would run when deployed. Use this to test
+  your function logic before deploying.
+
+  Provide test data via --data (inline JSON), --file (JSON file), or --document-id (fetch from Sanity). For update
+  events, use the before/after flag pairs to simulate document changes.
+
 EXAMPLES
   $ sanity-run functions test <name> --data '{ "id": 1 }'
 
@@ -526,7 +640,7 @@ EXAMPLES
   $ sanity-run functions test <name> --event update --data-before '{ "title": "before" }' --data-after '{ "title": "after" }'
 ```
 
-_See code: [src/commands/functions/test.ts](https://github.com/sanity-io/runtime-cli/blob/v12.3.0/src/commands/functions/test.ts)_
+_See code: [src/commands/functions/test.ts](https://github.com/sanity-io/runtime-cli/blob/v13.0.0/src/commands/functions/test.ts)_
 
 ## `sanity-run help [COMMAND]`
 

package/dist/actions/blueprints/assets.d.ts

@@ -1,10 +1,12 @@
 import AdmZip from 'adm-zip';
+import type { Logger } from '../../utils/logger.js';
 import type { AuthParams, CollectionFunction, FunctionResource } from '../../utils/types.js';
 export declare const ASSET_CHECK_URL: string;
 export declare const ASSET_STASH_URL: string;
-export declare function stashAsset({ resource, auth, }: {
+export declare function stashAsset({ resource, auth, logger, }: {
     resource: FunctionResource | CollectionFunction;
     auth: AuthParams;
+    logger: ReturnType<typeof Logger>;
 }): Promise<{
     success: boolean;
     assetId?: string;

package/dist/actions/blueprints/assets.js

@@ -10,6 +10,7 @@ import { resolveResourceDependencies } from '../../utils/functions/resolve-depen
 import { shouldAutoResolveDependencies } from '../../utils/functions/should-auto-resolve-deps.js';
 import { shouldTranspileFunction } from '../../utils/functions/should-transpile.js';
 import getHeaders from '../../utils/get-headers.js';
+import { createTracedFetch } from '../../utils/traced-fetch.js';
 import { transpileFunction } from '../../utils/transpile/transpile-function.js';
 import { isLocalFunctionCollection } from '../../utils/types.js';
 const { apiUrl } = config;
@@ -17,10 +18,11 @@ const ASSETS_URL = `${apiUrl}vX/blueprints/assets`;
 export const ASSET_CHECK_URL = `${ASSETS_URL}/check`;
 export const ASSET_STASH_URL = `${ASSETS_URL}/stash`;
 const MAX_ASSET_SIZE = 209_715_200; // 200 MB in bytes
-export async function stashAsset({ resource, auth, }) {
+export async function stashAsset({ resource, auth, logger, }) {
     const isCollection = isLocalFunctionCollection(resource);
     const functions = isCollection ? resource.functions : [resource];
     const combinedAsset = [];
+    const prepareErrors = [];
     try {
         for (const func of functions) {
             const prepResult = await prepareAsset({ resource: func, auth });
@@ -30,13 +32,18 @@ export async function stashAsset({ resource, auth, }) {
                     partAsset: { outputPath: prepResult.outputPath, cleanup: prepResult.cleanup },
                 });
             }
+            else if (prepResult.error) {
+                prepareErrors.push({ name: func.name, error: prepResult.error });
+            }
         }
         if (combinedAsset.length !== functions.length) {
             const processedNames = new Set(combinedAsset.map((asset) => asset.name));
             const failedFunctions = functions.filter((func) => !processedNames.has(func.name));
+            const failedNames = failedFunctions.map((f) => f.name).join(', ');
+            const errorDetails = prepareErrors.map((e) => `${e.name}: ${e.error}`).join('; ');
             return {
                 success: false,
-                error: `Failed to prepare ${failedFunctions.length} function(s) in collection: ${failedFunctions.map((f) => f.name).join(', ')}`,
+                error: `Failed to prepare ${failedFunctions.length} function(s) in blueprint: ${failedNames}${errorDetails ? `. Details: ${errorDetails}` : ''}`,
             };
         }
         let result = { success: false };
@@ -48,6 +55,7 @@ export async function stashAsset({ resource, auth, }) {
                     cleanup: combinedResult.cleanup,
                     resource: resource,
                     auth,
+                    logger,
                     collectionInfo: {
                         name: resource.name,
                         functionCount: resource.functions.length,
@@ -64,6 +72,7 @@ export async function stashAsset({ resource, auth, }) {
                 cleanup: combinedAsset[0].partAsset.cleanup,
                 resource: resource,
                 auth,
+                logger,
             });
         }
         return result;
@@ -149,11 +158,12 @@ async function combineAssets(allAssets) {
         return { error: err instanceof Error ? err.message : `${err}` };
     }
 }
-async function stashSingleAsset({ outputPath, cleanup, resource, auth, collectionInfo, }) {
+async function stashSingleAsset({ outputPath, cleanup, resource, auth, logger, collectionInfo, }) {
+    const fetchFn = createTracedFetch(logger);
     try {
         const { b64, hash } = await pathToB64ZipHash(outputPath);
         try {
-            const checkResponse = await fetch(`${ASSET_CHECK_URL}/${hash}`, {
+            const checkResponse = await fetchFn(`${ASSET_CHECK_URL}/${hash}`, {
                 method: 'GET',
                 headers: getHeaders(auth),
             });
@@ -164,7 +174,7 @@ async function stashSingleAsset({ outputPath, cleanup, resource, auth, collectio
         }
         catch { } // Continue to stash the Asset
         // Asset doesn't exist, so stash it
-        const assetResponse = await fetch(ASSET_STASH_URL, {
+        const assetResponse = await fetchFn(ASSET_STASH_URL, {
             method: 'POST',
             headers: getHeaders(auth),
             body: JSON.stringify({