You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: improve error quality and prevent token leak in telemetry (#279)
## Summary
Fixes three of the highest-impact issues from the 0.11.0 release
(sourced from Sentry production data).
### fix(issue): actionable error when issue not found by numeric ID
(CLI-N)
**118 events / 41 users**
`getIssue()` surfaces a bare 404 as a generic message with no indication
of which ID failed. Users often confuse numeric Sentry group IDs (which
require access) with short-ID suffixes (which are human-readable).
Now `resolveIssue()` catches the 404 in both the `numeric` and
`explicit-org-numeric` cases and re-throws a `ContextError` with:
- The exact ID that wasn't found
- A note that access may be missing or the issue may be deleted
- A suggestion to try the `<project>-<id>` short-ID format
### fix(telemetry): redact `--token` value from telemetry tags (CLI-19)
**Security — token values were being sent to Sentry**
`setFlagContext()` in `telemetry.ts` was forwarding the raw value of
every flag as a `flag.<name>` tag. For `sentry auth login --token
sntrys_...`, this meant the actual API token was appearing in the
`flag.token` tag on every telemetry event.
Adds a `SENSITIVE_FLAGS` set (currently: `token`) and replaces those tag
values with `[REDACTED]` before the tag is set.
### fix(issue list): validate `--cursor` format before hitting the API
(CLI-7H/7P/7B)
**21 events / 12 users — 400 Bad Request from API**
`--cursor 100` (a plain integer) was forwarded directly to the API,
which rejects it. Cursor values are opaque strings like
`1735689600:0:0`. Plain-integer inputs are now rejected at parse time
with a message explaining the expected format.
Note: the `--limit` part of this bug is already addressed on main via
auto-pagination (#274).
0 commit comments