Packages

@sentry/cli

3.8.2 · 22 Oct 2026FSL-1.1-MIT24.7M / weekRepositoryHomepagenpmAtom feed

Upgrading @sentry/cli from 2.58.1 to 2.58.6

5 releases in betweennotes for 3

Other targets from 2.58.1Latest3.8.2
?
changes to make
0
advisories fixed
3+
new
3+
fixes

Counted from 3 of 5 release notes. Advisories are counted from the advisory database, in full.

Release by release

  1. 2.58.5 – 2.58.62 releases, no release note

  2. 2.58.4

    12 Dec 20251 fix
    • fixed

      Use node directly in the postinstall script, instead of using npm run (#3030). This change ensures the postinstall script remains compatible with package managers other than npm.

  3. 2.58.3

    10 Dec 20252 new · 1 fix
    • new

      For the sentry-cli build upload command, we now only auto-detect Git metadata when we detect we are running in a CI environment, unless the user manually overrides this behavior (#2974). This change prevents local development builds from triggiering GitHub status checks for size analysis.

    • new

      The sentry-cli build upload command now automatically detects the correct branch or tag reference in non-PR GitHub Actions workflows (#2976). Previously, --head-ref was only auto-detected for pull request workflows. Now it works for push, release, and other workflow types by using the GITHUB_REF_NAME environment variable.

    • fixed

      Fixed a bug where the sentry-cli sourcemaps inject command could inject JavaScript code into certain incorrectly formatted source map files, corrupting their JSON structure (#3003).

  4. 2.58.2

    12 Nov 20251 new · 1 fix
    • new

      Added validation for the sentry-cli build upload command's --head-sha and --base-sha arguments (#2945). The CLI now validates that these are valid SHA1 sums. Passing an empty string is also allowed; this prevents the default values from being used, causing the values to instead be unset.

    • fixed

      Fixed a bug where providing empty-string values for the sentry-cli build upload command's --vcs-provider, --head-repo-name, --head-ref, --base-ref, and --base-repo-name arguments resulted in 400 errors (#2946). Now, setting these to empty strings instead explicitly clears the default value we would set otherwise, as expected.