@posthog/cli 0.8.1 → 0.8.3

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # posthog-cli
 
+## 0.8.3 — 2026-07-15
+
+### Patch changes
+
+- [97457ef9b4](https://github.com/PostHog/posthog/commit/97457ef9b493debd3975f12b8b6d1c4baaee2d93) Sourcemap upload concurrency can now be configured with `--concurrency` or `POSTHOG_CLI_SOURCEMAP_UPLOAD_CONCURRENCY`, while keeping the existing default of 10 uploads at a time. — Thanks @DebadityaHait!
+
+## 0.8.2 — 2026-07-13
+
+### Patch changes
+
+- [e38163eaab](https://github.com/PostHog/posthog/commit/e38163eaab6d1120f3c87fc2c38f2772ee9cadf2) Fix concurrent release creation and multipart symbol uploads — Thanks @ablaszkiewicz!
+
 ## 0.8.1 — 2026-07-06
 
 ### Patch changes

package/README.md

@@ -1,5 +1,25 @@
 # The Posthog CLI
 
+The command line interface for PostHog. Exposes PostHog's MCP tool catalog through a shell-friendly interface, handles debug symbol uploads for error tracking, and more. For full documentation, see [our CLI docs](https://posthog.com/docs/cli).
+
+## Installation
+
+Install the PostHog CLI with our wizard by running this command:
+
+```bash
+npx -y @posthog/wizard@latest cli add
+```
+
+If you'd rather not use our wizard, you can install the CLI by running:
+
+```bash
+npm install -g @posthog/cli@latest
+```
+
+Note: if you are installing the CLI for use with a coding agent, you should follow our [setup for agents](https://posthog.com/docs/cli#setup-for-agents) instructions.
+
+## Usage
+
 ```bash
 > posthog-cli --help
 The command line interface for PostHog 🦔
@@ -7,17 +27,25 @@ The command line interface for PostHog 🦔
 Usage: posthog-cli [OPTIONS] <COMMAND>
 
 Commands:
-  login      Interactively authenticate with PostHog, storing a personal API token locally. You can also use the environment variables `POSTHOG_CLI_API_KEY`, `POSTHOG_CLI_PROJECT_ID` and `POSTHOG_CLI_HOST`
-  query      Run a SQL query against any data you have in posthog. This is mostly for fun, and subject to change
-  sourcemap  Upload a directory of bundled chunks to PostHog
-  exp        Contains a set of experimental commands
-  help       Print this message or the help of the given subcommand(s)
+  login        Interactively authenticate with PostHog, storing a personal API token locally. You can also use the environment variables `POSTHOG_CLI_API_KEY` and `POSTHOG_CLI_PROJECT_ID`
+  exp          Experimental commands, not quite ready for prime time
+  sourcemap    Upload a directory of bundled chunks to PostHog
+  dsym         Upload Apple dSYM debug symbol files to PostHog
+  hermes       Upload hermes sourcemaps to PostHog
+  proguard     Upload proguard mapping files to PostHog
+  symbol-sets  Upload, download, and manage symbol sets
+  api          Agent-first PostHog API tools
+  help         Print this message or the help of the given subcommand(s)
 
 Options:
-      --host <HOST>  The PostHog host to connect to [default: https://us.posthog.com]
-      --dry-run      Skip artifact processing and upload without contacting PostHog or requiring credentials
-  -h, --help         Print help
-  -V, --version      Print version
+      --host <HOST>              The PostHog host to connect to
+      --no-fail                  Disable non-zero exit codes on errors. Use with caution
+      --skip-ssl-verification    Skip SSL certificate verification when talking to the PostHog API. Use only with self-signed certificates
+      --rate-limit <RATE_LIMIT>  Set the number of requests per minute for the Posthog API Client [env: POSTHOG_CLIENT_RATE_LIMIT=]
+      --dotenv-file <PATH>       Load PostHog credentials from this dotenv-style file when not present in the process environment. Prefer this over the `--env-file` alias: the npm package runs the binary through a `node` wrapper, and Node's own built-in `--env-file` flag intercepts that spelling
+      --dry-run[=<DRY_RUN>]      Skip artifact processing and upload (sourcemap, dSYM, hermes, proguard) without contacting PostHog or requiring credentials. Intended for CI gates that bundle to catch regressions but must not (or cannot) upload. Not for release builds. Pass it before the subcommand (`posthog-cli --dry-run hermes upload ...`) or set `POSTHOG_CLI_DRY_RUN`. This is distinct from the `exp endpoints` `--dry-run`, which previews endpoint changes [env: POSTHOG_CLI_DRY_RUN=] [default: false] [possible values: true, false]
+  -h, --help                     Print help
+  -V, --version                  Print version
 ```
 
 ## Env-based Authentication
@@ -44,6 +72,22 @@ Pass `--include-source` to bundle the referenced source files for richer context
 
 The standalone `posthog-cli dsym upload` command is unchanged and still recommended for dSYM-only Xcode build phases, where it also reads release and version metadata from each bundle's `Info.plist`.
 
+## Configuring sourcemap upload concurrency
+
+Sourcemap uploads run up to 10 file uploads at a time by default. Set a different positive value with `--concurrency` on `sourcemap upload` or `sourcemap process`:
+
+```bash
+posthog-cli sourcemap process --directory ./dist --concurrency 32
+```
+
+For build integrations such as `@posthog/nextjs-config`, set `POSTHOG_CLI_SOURCEMAP_UPLOAD_CONCURRENCY` in the build environment instead:
+
+```bash
+POSTHOG_CLI_SOURCEMAP_UPLOAD_CONCURRENCY=32 npm run build
+```
+
+The CLI flag takes precedence over the environment variable. Both require a value greater than zero. This setting applies only to plain sourcemap uploads; other CLI concurrency remains unchanged.
+
 ## Skipping uploads (dry run)
 
 Pass `--dry-run` before the subcommand (`posthog-cli --dry-run hermes upload ...`), or set `POSTHOG_CLI_DRY_RUN=true`, to turn the upload commands — `sourcemap`, `dsym`, `hermes`, and `proguard` — into a no-op.