Skip to content

:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.

34.9 KB
Raw Blame

posthog-cli

0.19.3 — 2026-11-04

Patch changes

  • 48fd6d2c7cc Stop reporting Next.js Turbopack server page stubs as a possible bundler misconfiguration when sourcemap upload skips their empty source maps — Thanks @JamesPatrickGill!

0.19.2 — 2026-11-03

Patch changes

  • 5d6bc49b864 Return a credentials error that names POSTHOG_HOME and the env credential variables, instead of panicking, when no home directory can be found — Thanks @posthog[bot]!

0.19.1 — 2026-11-02

Patch changes

  • e5ddfc79ecf Keep the release that hermes inject stamped when hermes clone runs in symbol-set mode without release flags — Thanks @rafaeelaudibert!

0.19.0 — 2026-10-28

Minor changes

0.18.12 — 2026-10-21

Patch changes

0.18.11 — 2026-10-20

Patch changes

0.18.10 — 2026-10-07

Patch changes

  • 7c55058c01a Upload native bundler debug IDs without rewriting source files, and skip files without uploadable IDs instead of failing CI — Thanks @hpouillot!

0.18.9 — 2026-09-28

Patch changes

  • 3587ad4eb53 Upload symbol sets with a presigned PUT when the server offers one. Presigned POST is an AWS S3 extension, so instances whose object storage does not implement it rejected every symbol set upload with 501 NotImplemented. The multipart POST stays in place for older servers. — Thanks @hpouillot!

0.18.8 — 2026-09-28

Patch changes

  • 09644fddca4 Read the remote URL from the [remote "..."] sections of the Git config only, and prefer origin. A repository that records another URL in its config, such as a superproject that records the URL of a submodule, no longer gets the wrong remote URL and repository name in its release metadata. — Thanks @hpouillot!
  • 69a47659037 In event release mode, sourcemap upload no longer uploads unchanged chunks again when the bundler names chunks by content, as Vite does by default. Every chunk carries the release id, so every release renamed every chunk, and the content hash covered those names: the map's file, the sourceMappingURL comment and imports of other chunks. The hash now leaves out script file paths (ending in .js, .mjs or .cjs). Hashes stored by earlier versions include the paths, so the first upload after updating sends each chunk once more. — Thanks @ablaszkiewicz!

0.18.7 — 2026-09-24

Patch changes

  • 0298cb7450a Add posthog-cli update. It updates in place when you installed with the install script, and prints the right command when npm, Homebrew or cargo owns the binary. The old posthog-cli-update is no longer installed; it could not reach a release and never worked. — Thanks @hpouillot!

0.18.6 — 2026-09-24

Patch changes

  • 4dedd8363d1 Publish to crates.io again, so cargo install posthog-cli gets the current version. The crate had been left on 0.5.11 since December. — Thanks @hpouillot!

0.18.5 — 2026-09-23

Patch changes

  • d9d6409aa72 Install with Homebrew: brew install posthog/tap/posthog-cli. Installers now download from releases.posthog.com, falling back to GitHub Releases. — Thanks @hpouillot!

0.18.4 — 2026-09-23

Patch changes

0.18.3 — 2026-09-16

Patch changes

  • b6486bfe18a Stop reporting expected sourcemap upload outcomes as warnings. Missing releases and skipped empty sourcemaps now use lower log levels when uploads continue. — Thanks @posthog[bot]!

0.18.2 — 2026-09-11

Patch changes

  • 342f1f1c551 Ask the server which chunks it still needs before starting upload batches. A build whose chunks are mostly already uploaded now makes a few API calls instead of two per batch of 50. — Thanks @ablaszkiewicz!

0.18.1 — 2026-09-07

Patch changes

  • fcbcec2ef4d Remove credentials from the git remote URL stored in release metadata. Rotate any token an earlier version stored. — Thanks @ablaszkiewicz!

0.18.0 — 2026-09-02

Minor changes

  • fb9ed9d8ec1 Default --release-mode to event for sourcemap inject, sourcemap process, sourcemap upload, hermes inject, hermes clone and hermes upload. Uploaded symbol sets and source maps are now release-independent, and each exception resolves its own release: a web build reads the _posthogReleaseId injected into the chunk, and a Hermes build resolves it from the $app_namespace / $app_version / $app_build the SDK already sends. Two releases that ship the same code keep one symbol set instead of colliding on the release that uploaded it first. Pass --release-mode symbol-set to keep binding the release to what you upload. Before upgrading, check that the release coordinates you pass match the app's bundle identifier or applicationId, version and build number, because a mismatch leaves exceptions with no release.

    hermes upload now resolves --info-plist before it checks the release coordinates. An iOS build that supplies them that way no longer gets a warning about a release the run creates correctly. — Thanks @ablaszkiewicz!

0.17.0 — 2026-09-02

Minor changes

  • 8a28e07ea71 Deprecate --release-mode on proguard upload and --no-release-bind on dsym upload. Both flags are hidden no-ops now: each command uploads its symbol sets bound to the release it creates, which is what it did before the flags existed. A supplied flag prints a deprecation warning instead of changing the upload, so a released gradle plugin or upload-symbols.sh that still passes one keeps working. proguard upload no longer reads POSTHOG_RELEASE_MODE; the variable keeps steering sourcemap inject, sourcemap process, sourcemap upload, hermes inject, hermes clone and hermes upload.

    Event mode pays off when two releases ship a byte-identical artifact. A proguard map id is a hash of the mapping, and a dSYM symbol set is keyed on the Mach-O LC_UUID, so an ordinary release that changes code already gets its own symbol set. The dSYM path also lost release attribution for embedded targets, because one upload covers every target's dSYM but creates one release. — Thanks @ablaszkiewicz!

0.16.2 — 2026-09-01

Patch changes

  • 13dc107a02b Fix a race in sourcemap process: the source pairs are now read from disk once, injected, and the same in-memory pairs are uploaded. Previously inject and upload each re-walked the directory roots, so a bundler writing into the scanned directory mid-run (e.g. Turbopack's background filesystem-cache flush on Next.js 16.3+) could hand the upload pass chunks the inject pass never stamped, aborting the whole run with "Chunk ID not found". That error now names the offending file and says how to recover. --delete-after cleanup no longer fails the build when a file vanished or was replaced after upload: such pairs are skipped with a warning, and a replaced file's artifacts are left untouched instead of being stripped or deleted. Overlapping selection roots now process each file once instead of stamping it repeatedly. The "injecting selection" log line is bounded instead of printing every selected path, since a large stdin-provided selection used to produce a log line big enough to kill the CLI when stderr was a non-blocking pipe (e.g. spawned from Node.js). — Thanks @cat-ph!

0.16.1 — 2026-09-01

Patch changes

  • 0a93bb9d822 Fix --release-mode event keeping a stale source map for a chunk that gains a release. The content hash ignored which snippet the chunk carried. The release snippet is longer than the chunk-id snippet, so it shifts the generated columns the uploaded map records. The two uploads therefore shared one hash, the server kept the first map, and later frames resolved to the wrong source positions. The hash now covers the snippet variant. It still ignores the release id itself, so a new release does not re-upload every chunk. — Thanks @ablaszkiewicz!

0.16.0 — 2026-08-26

Minor changes

  • db85d262555 Add --release-mode to hermes clone and hermes upload. event leaves the uploaded Hermes source maps release-independent, so a React Native build that ships unchanged JavaScript across two releases keeps one symbol set instead of colliding on the release the first upload stamped on it. Each exception resolves its own release from the $app_namespace / $app_version / $app_build the SDK already sends, so pass --release-name, --release-version and --build matching the app's bundle identifier or applicationId, version and build number. symbol-set stays the default. hermes inject --release-mode=event no longer errors: it injects content-addressed chunk ids and, unlike a web build, embeds no release id, because a Hermes bytecode bundle has nothing to read one back out. — Thanks @ablaszkiewicz!

0.15.1 — 2026-08-24

Patch changes

0.15.0 — 2026-08-24

Minor changes

0.14.1 — 2026-08-23

Patch changes

  • 5e488e12013 Accept sourcemaps that use the camel-case chunkId field when cloning or uploading Hermes sourcemaps. — Thanks @marandaneto!

0.14.0 — 2026-08-21

Minor changes

  • 7dd3d0f5c27 With --release-mode=event, sourcemap inject now adopts a bundler-emitted ECMA-426 debug id (//# debugId= comment or the sourcemap's debugId field) as the chunk id instead of deriving its own, so one id identifies the chunk across the toolchain. The sourcemap's debugId field is preserved on save instead of being renamed to chunk_id, a bundler-stamped debug id no longer makes inject skip the mapping adjustment for the injected snippet, and hermes uploads still accept maps that carry only a debugId. Behavior change: sourcemap upload --hermes now fails with an error when it finds no maps carrying a chunk id or debug id, instead of exiting successfully having uploaded nothing. — Thanks @ablaszkiewicz!

0.13.3 — 2026-08-20

Patch changes

  • ee7d6424091 Linux release binaries now embed a GNU build id, so native crash reports from the CLI can be matched to uploaded debug symbols. — Thanks @ablaszkiewicz!

0.13.2 — 2026-08-20

Patch changes

  • 029c984bdef Retry symbol set uploads through the standard S3 endpoint when the transfer-acceleration endpoint is unreachable, so uploads complete on networks that block the accelerate domain. A 5 second connect timeout on uploads makes unreachable endpoints fail fast. — Thanks @ablaszkiewicz!

0.13.1 — 2026-08-20

Patch changes

  • fd234e17b30 Improve CLI error diagnostics with native stack symbolication metadata, release debug symbols, and structured categories for local file and parsing failures. — Thanks @hpouillot!

0.13.0 — 2026-08-18

Minor changes

  • f0be634b15f Add --release-mode to proguard upload, matching sourcemap upload. symbol-set (the default) keeps stamping the release onto the uploaded mapping. EXPERIMENTAL event creates the release but leaves the mapping unbound, so each event resolves its own release from the app version and namespace the SDK already sends. A map id is derived from the mapping's own content, so this keeps one symbol set for a mapping that several releases share. Also settable via POSTHOG_RELEASE_MODE. — Thanks @ablaszkiewicz!

0.12.0 — 2026-08-18

Minor changes

  • 45016b12515 Add posthog-cli release resolve, which prints the id of the release the current build belongs to and creates the release if it doesn't exist yet. Only the id goes to stdout, so RELEASE_ID=$(posthog-cli release resolve) works; --json prints the whole release. It resolves the same release sourcemap inject would, so a bundler plugin that injects the release id into chunks itself lands on the same row. When nothing identifies a release, it prints nothing and exits 0. --dry-run skips it, since resolving a release can create one. — Thanks @ablaszkiewicz!

Patch changes

  • 90730d20684 Delete CSS source maps and remove their sourceMappingURL comments after upload — Thanks @marandaneto!

0.11.3 — 2026-08-17

Patch changes

  • 617ed9c912a Derive the --release-mode event chunk id from the minified source alone, and overwrite a symbol set whose content changed instead of failing. Bundlers embed the original file in sourcesContent, so a comment-only edit rewrote the sourcemap and, with the map folded into the id, minted a new chunk for code that never changed. The content hash still covers source and map, so that edit re-uploads the chunk under its existing id. Chunk ids injected by earlier versions change once on the next build, which re-uploads those chunks under their new ids. --skip-on-conflict is now ignored in this mode, with a warning: every chunk carries the release id in its injected snippet, so every chunk conflicts on every release, and skipping them all would leave the previous release id in place. — Thanks @ablaszkiewicz!

0.11.2 — 2026-08-14

Patch changes

  • 751c7c08aa2 Upload one symbol set per chunk id when processing sourcemaps. In --release-mode event a bundler that copies an entry point to a second name (a hashless alias beside app-<hash>.js) produces two byte-identical files that share a sourcemap, and so one content-addressed chunk id twice, which the bulk-start endpoint rejects as invalid_chunk_ids. — Thanks @ablaszkiewicz!

0.11.1 — 2026-08-13

Patch changes

  • c75bed06227 Retry transient GitHub release download failures with exponential backoff when installing @posthog/cli from npm. — Thanks @marandaneto!

0.11.0 — 2026-08-12

Minor changes

  • 8d58ef5de6c Add --release-mode (env POSTHOG_RELEASE_MODE) to inject/upload/process. The default symbol-set keeps the existing behavior: the release id is stamped onto the uploaded symbol sets. The experimental event mode derives content-addressed chunk ids that stay stable across rebuilds and injects the release id into each JS chunk as _posthogReleaseId, so the SDK reports it per event and symbol sets stay release-independent. The release is still created; it just isn't bound to any chunk. — Thanks @ablaszkiewicz!

0.10.0 — 2026-08-03

Minor changes

  • 2c588c9673 Add --no-release-bind to dsym upload: the release is still created, but uploaded symbol sets stay release-independent. — Thanks @ablaszkiewicz!

0.9.4 — 2026-07-30

Patch changes

  • a29315a19c Sourcemap, dSYM, and ProGuard uploads now end with a single per-run summary line reporting how many chunks were uploaded, skipped as already present on the server, and skipped as too large. The summary is logged even when a run fails partway, and the same counts are attached to the error_tracking_cli_sourcemaps_upload_finished telemetry event so skip rates are queryable. — Thanks @ablaszkiewicz!

0.9.3 — 2026-07-30

Patch changes

  • ccd7de59e0 Symbol set uploads (sourcemap upload, sourcemap upload-hermes, symbol-sets upload, dSYM and Proguard uploads) are now significantly faster: chunk uploads reuse a single HTTP connection pool instead of opening a fresh TLS connection per chunk, payload content hashes are computed once (in parallel) instead of twice per file, and sourcemap payload preparation (serialization + compression) runs across all cores. — Thanks @hpouillot!

0.9.2 — 2026-07-28

Patch changes

  • d871ba0d38 Fixed posthog-cli api commands crashing on Windows when loading the bundled Node.js script. — Thanks @cvolzer3!

0.9.1 — 2026-07-23

Patch changes

  • 1e49417142 Publish fresh CLI artifacts after fixing repository paths that prevented the Windows release build from checking out the source. — Thanks @cat-ph!

0.9.0 — 2026-07-22

Minor changes

  • 845de8f80c symbol-sets upload now accepts standalone Mach-O executables and dylibs, not just ELF files and .dSYM bundles. Binaries that embed their own DWARF — Go binaries on macOS, which never produce a dSYM (dsymutil reports "no debug symbols in executable") — upload directly, with the LC_UUID as the symbol set id. Universal (fat) binaries upload one symbol set per architecture slice. Go's default darwin build compresses the embedded DWARF, which the server cannot read yet; such binaries are skipped with guidance to rebuild with -ldflags=-compressdwarf=false. — Thanks @cat-ph!

0.8.5 — 2026-07-21

Patch changes

  • f3a3420b95 posthog-cli api failures are now diagnosable and attributable. Launch failures report the specific cause (bundle not embedded in the build, no home directory, install-directory write failure with the underlying IO error kind, Node.js missing) both in the error message and in error telemetry, instead of one generic bundle-not-found error. When the proxied Node process fails, the CLI now exits through its normal path — flushing telemetry and honoring --no-fail — instead of terminating immediately, and the bundled API CLI flushes its own analytics before exiting non-zero so failed calls are no longer silently dropped. The api command also emits the standard command-run usage event and attaches the project id from POSTHOG_CLI_PROJECT_ID/POSTHOG_CLI_ENV_ID to telemetry when stored credentials are not used. — Thanks @cvolzer3!

0.8.4 — 2026-07-16

Patch changes

  • f45778f281 The dotenv credentials file can now also be pointed at with the POSTHOG_CLI_DOTENV_FILE environment variable, equivalent to passing --dotenv-file — for callers that control the environment but not the command line (e.g. an Xcode build phase invoking the iOS SDK's upload-symbols.sh). — Thanks @ablaszkiewicz!

0.8.3 — 2026-07-15

Patch changes

  • 97457ef9b4 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

0.8.1 — 2026-07-06

Minor changes

  • 066d914497 symbol-sets upload now also accepts Apple .dSYM bundles, packaging them through the same path as dsym upload (uppercase UUID chunk_ids, AppleDsym container). A single posthog-cli symbol-sets upload --directory <dir> run uploads both Linux ELF debug symbols and macOS dSYMs, so native symbol uploads no longer need a different command per platform. The dSYM branch shells out to dwarfdump (Xcode, macOS-only); when it is unavailable the bundle is reported and skipped while ELF symbols in the same directory still upload. The standalone dsym upload command is unchanged. — Thanks @cat-ph!

Patch changes

0.8.0 — 2026-07-03

Never published: the release pipeline's Windows build failed after the version bump landed, so no tag, GitHub release, or npm package exists for this version. Its changes first shipped in 0.8.1.

0.7.34 — 2026-06-30

Patch changes

  • 889dd51553 Strip sourceMappingURL comments when deleting uploaded source maps — Thanks @hpouillot!

0.7.33 — 2026-06-25

Patch changes

  • c334e9f9c3 Mention Go's -ldflags=-B=gobuildid when symbol-sets upload finds ELF files without a GNU build id, since Go binaries don't emit one by default. — Thanks @cat-ph!
  • b9097541d4 Allow explicit sourcemap release uploads to continue when optional Git metadata cannot be read — Thanks @cat-ph!

0.7.32 — 2026-06-24

Patch changes

  • 6fb4456e8f Fix the CLI release workflow so the Windows (x86_64-pc-windows-msvc) build succeeds and ships with each release. — Thanks @cat-ph!
  • dfd1f66a9f Add symbol-sets upload for native (ELF) debug symbols: it scans a directory for executables, shared libraries, and objcopy --only-keep-debug companions that carry a GNU build id and uploads them to PostHog. — Thanks @cat-ph!

0.7.31 — 2026-06-24

Never published: the release pipeline's Windows build failed after the version bump landed, so no tag, GitHub release, or npm package exists for this version. Its changes first shipped in 0.7.32.

0.7.30 — 2026-06-22

Patch changes

  • d51a877525 Handle Git worktrees and packed refs when detecting repository info — Thanks @hpouillot!

0.7.29 — 2026-06-19

Patch changes

0.7.28 — 2026-06-18

Patch changes

  • f0bb5426d5 Remove the posthog-cli api experimental opt-in and skip unavailable generated tools without warning noise. — Thanks @cvolzer3!

0.7.27 — 2026-06-18

Patch changes

  • 7be64cbe1e Fix the post-login hint so posthog-cli login suggests a valid next command based on the scopes authorized for the generated key. — Thanks @cvolzer3!

0.7.26 — 2026-06-18

Patch changes

  • 801e9a763c Fix CLI login for agent workflows by adding the Agent CLI preset, using the supported agent scope set, and showing clearer messages about what the generated key can do. — Thanks @cvolzer3!

0.7.25 — 2026-06-17

Patch changes

0.7.24 — 2026-06-16

Patch changes

0.7.23 — 2026-06-15

Patch changes

0.7.22 — 2026-06-09

Patch changes

0.7.21 — 2026-06-05

Patch changes

0.7.20 — 2026-06-05

Patch changes

0.7.19 — 2026-06-04

Patch changes

0.7.18

  • fix: rename --env-file to --dotenv-file. The npm package runs the CLI binary through a node wrapper script, and Node has its own built-in --env-file flag — so Node intercepted the flag before it reached the binary, failing with node: .env: not found for a missing file. --env-file still works as an alias for native installs.

0.7.17

  • fix: treat a missing --env-file as a warning instead of a fatal error — the CLI logs that the file wasn't found and falls back to the other credential sources (process env, then stored credentials). A file that exists but can't be read still errors.

0.7.16

  • feat: add --dry-run flag (and POSTHOG_CLI_DRY_RUN env var) to skip artifact uploads (sourcemap, dSYM, Hermes, ProGuard) without contacting PostHog or requiring credentials — for CI gates that bundle to catch regressions but must not upload.

0.7.15

  • fix: make symbol upload retry logs clearer and report failed finalization explicitly.

0.7.14

  • feat: add --env-file <PATH> to load POSTHOG_CLI_HOST, POSTHOG_CLI_API_KEY, and POSTHOG_CLI_PROJECT_ID (and their legacy aliases) from a dotenv-style file when not set in the process environment. Credentials are resolved atomically from a single source (process env first, then the file), so POSTHOG_CLI_HOST from the file cannot redirect a key supplied by the process env.

0.7.13

  • chore: bump cargo-dist to 0.32.0; the new npm installer drops the bundled transitive deps that were carrying open CVEs (axios, follow-redirects, minimatch, brace-expansion)

0.7.12

  • feat: add --skip-on-conflict to symbol upload commands for keeping existing symbol sets when content differs
  • feat: add --force to sourcemap, Hermes, and ProGuard uploads for explicit content overwrites

0.7.11

  • fix: resolve release once in process command to avoid race condition when multiple workers run in parallel
  • fix: skip synthetic Swift CU names (e.g. <swift-imported-modules>) before joining with comp_dir so they no longer dominate the project-root prefix and reject real source files

0.7.10

  • feat: add symbol-sets download command to download symbol sets by ID or ref
  • feat: add symbol-sets extract command for local file extraction
  • fix: prevent ZIP path traversal in dSYM extraction
  • fix: validate symbol set ID is a UUID before download

0.7.9

  • feat: warn and skip empty sourcemaps (no mappings/sources/names) during upload to surface bundler misconfigurations instead of silently uploading useless symbol sets

0.7.8

  • feat: add --build flag to all upload commands (hermes, dsym, proguard, sourcemap) via shared ReleaseArgs
  • feat: build number packed into version string ("1.0+42") for release uniqueness; UI splits on + to display version and build separately

0.7.7

  • fix: align dsym upload release flags with other upload commands by using --release-name / --release-version (with backward-compatible aliases)
  • fix: reuse shared release args in dsym upload so release fallback behavior matches other upload commands

0.7.5

  • fix: stable source bundle for dSYM uploads — CU-anchored prefix filter prevents framework sources from changing the content hash
  • fix: thin fat dSYM binaries per arch before zipping so sibling arch rebuilds don't cause content_hash_mismatch
  • fix: add --force flag to allow overwriting symbol sets whose content has changed

0.7.4

  • fix: create per-UUID ZIP for dSYM uploads

0.7.3

  • feat: enable symbol set compression
  • fix: fix process command reading from stdin

0.7.2

  • feat: allow reading files and directories from stdin

0.7.1

  • feat: track upload started and upload finished events

0.7.0

  • feat: promote dsym, hermes, and proguard commands from experimental to top-level
  • feat: keep backward-compat aliases under exp (hidden from help)

0.6.2

  • fix: endpoints now save to YAML with proper newlines

0.6.1

  • chore: bump cargo-dist version

0.6.0

  • Add experimental dSYM upload for iOS/macOS crash symbolication

0.5.30

  • Add experimental dSYM upload for iOS/macOS crash symbolication

0.5.29

  • chore: introduce env variable POSTHOG_CLI_API_KEY and POSTHOG_CLI_PROJECT_ID (backwards compatible)

0.5.28

  • chore: introduce --release-name and --release-version options (backwards compatible)

0.5.27

  • fix: only warns on release id mismatch errors

0.5.26

  • feat: use env variables provided by github actions when available

0.5.24

  • chore: add endpoints use case to cli auth flow

0.5.23

  • feat: add experimental commands for endpoints management

0.5.22

  • feat: add --project and --version to upload command to define release

0.5.20

  • chore: add global --rate-limit option for Posthog client

0.5.19

  • chore: upgrade cargo-dist to 0.30.3

0.5.18

  • fix: fix git info parsing in vercel environment

0.5.17

  • feat: add --file option to target built files directly

0.5.16

  • fix: cut a new version for fixing compromised package

0.5.15

  • Compromised

0.5.14

  • Fix authentication issue on sourcemap upload

0.5.13

  • Add --include option on sourcemap commands to match specific files inside directory

0.5.12

  • Bug fixes and improvements

0.5.11

  • Do not read bundle files as part of hermes sourcemap commands
  • Change hermes clone command to take two file paths (for the minified and composed maps respectively)

0.5.10

  • Add terminal checks for login and query command

0.5.9

  • Improve error handling from api
  • Reduce logs for sourcemap processing

0.5.8

  • Adding experimental support for proguard mappings

0.5.7

  • Fix bug where files point to the same sourcemap

0.5.6

  • Adding experimental support for hermes sourcemaps

0.5.5

  • When running inject command multiple times, we only update chunk ids when releases are different

0.5.4

  • Added no fail flag to disable non-zero exit codes on errors.

0.5.3

  • Add support for ignoring public path prefixes appended by bundlers to sourceMappingURLs when searching for sourcemaps associated with minified source code. Does not modify the sourceMappingURL as published.

0.5.2

  • Fixes a bug where chunks which shared a sourcemap were mishandled, leading to an error during upload in recent versions, and a silent failure in older versions. If you're using next, and saw an error message about "duplicate chunk IDs", this fix addresses that issue.

0.5.1

  • Attempts to reduce impact of previous breaking changes - re-adds --project and --version arguments to sourcemap upload command, marking them as no longer used

0.5.0

  • Sourcemap injection, upload and process commands made retriable. Significant improvement to release creation.

0.4.8

  • fix bug where directory ends with a javascript extension

0.4.4

  • process uploads in batches

0.4.3

  • add ignore argument to sourcemap inject, upload and process commands
  • add skip_ssl_verification argument for self-hosted instances

0.4.2

  • fix url encoded sourcemaps

0.4.1

  • add remote url to release metadata

0.4.0

  • extract sourcemap url from source code
  • add process command to inject and upload sourcemaps