Dashboard › cli › Distillation
7bcdbfcc-27a5-43c5-96c5-f5b56ba831c4["lore_tm_v1_aRsAtuLdiBOQ4bF7PuU_qGyl-demcIFKPvCxfAfemdo","lore_tm_v1_Pz0ga6agjS-48R82ayY0X4Erxt3sxdbZFL3cRVH3JNk","lore_tm_v1_N1YkmE7eGfjrgJdM_avisHEzsoTs6h8lx__lCXub-9g","lore_tm_v1_w10GB81lZxD8WqWhB7Wjfl0xzta045f5W4VcTPJtiIg","lore_tm_v1_hDPGe__lplaS9EoNJYGmBydu9wixR6xBcamv0unWNis","lore_tm_v1__Eh7EDzvg8npPEzdKzS6f9Of7Z-htXMSFv_DJ7-7tsY"]
Date: Sep 10, 2026
packages/cli/CONTRIBUTING.md states Sentry CLI follows gh CLI conventions: list commands use optional positional context with smart auto-detection; view commands use optional positional primary identifiers where possible; issue view requires an issue ID and event view requires an event ID.<org>/<project> for an explicit organization/project, <org>/ for all projects in an organization, <project> to search by project name across accessible organizations, and omission for DSN/config auto-detection.<org>/<project>) always win, 2. config defaults set via sentry config set, 3. DSN auto-detection from SENTRY_DSN or source code.--json; all view commands support -w/--web; list commands use --limit.ContextError from lib/errors.js for missing context, with the required entity, primary usage, and alternatives such as Set SENTRY_DSN for auto-detection.resolveOrg() or resolveOrgAndProject() from lib/resolve-target.ts, 3. support --json, 4. support -w/--web for view commands, 5. use ContextError for missing context, 6. add E2E tests under test/e2e/.package.json identifies workspace toolkit-cli-workspace version 0.0.0, uses packageManager: "pnpm@10.11.0", and requires Node >=20.0.packages/cli/package.json identifies package sentry version 0.45.0-dev.0, uses packageManager: "pnpm@10.11.0", requires Node >=20.0, and specifies development runtime Node >=22.15.packages/cli/package.json publishes binary sentry from ./dist/bin.cjs and includes dist/node-sqlite3-wasm.wasm, dist/assets/spleen-8x16.bin, and dist/vendor/symbolic_bg.wasm among its packaged artifacts.@stricli/core@1.2.8 → packages/cli/patches/@stricli%2Fcore@1.2.8.patch, @sentry/core@10.63.0 → packages/cli/patches/@sentry%2Fcore@10.63.0.patch, and @sentry/node-core@10.63.0 → packages/cli/patches/@sentry%2Fnode-core@10.63.0.patch; esbuild is the sole onlyBuiltDependencies entry.feat/toolkit-bridge-upgrade at 4a1d5bad105c006193c68459175f5eb3c7f78e08 has 16 modified files spanning upgrade source code and tests, totaling exactly 2,214 insertions and 336 deletions.04867eaf9 feat(cli): add toolkit upgrade bridge, 2. 9c874298e fix(cli): address toolkit bridge review, 3. 723375b6c fix(cli): address upgrade review findings, 4. dbee7e9f2 test(cli): update toolkit upgrade fixtures, 5. 5ffa5cd0f fix(cli): harden upgrade source resolution, 6. c8c815bbe fix(cli): validate GitHub release pagination, 7. b6484e0fb fix(cli): validate resolved upgrade metadata, 8. c6030fbf4 fix(cli): bind nightly manifests to versions, 9. 2f9b5d0d2 fix(cli): isolate pinned upgrade resolution, 10. 4a1d5bad1 test(cli): update pinned version fixture.4a1d5bad1 updates packages/cli/test/commands/cli.test.ts with exactly 1 insertion and 9 deletions.sentry cli upgrade nightly must switch to the nightly channel and update.sentry cli upgrade --offline as upgrading from cached patches with no network."stable" | "nightly" and treats a changed channel separately when deciding whether the resolved target already equals CLI_VERSION.uv_spawn may fail with EBUSY until the executable lock is released, so execution uses spawnWithRetry().