docs(cli): cover 0.7.7–0.7.10 - #65
Merged
Merged
Conversation
The CLI section stopped at 0.7.8 in the release notes and, in the reference pages, at 0.7.6: `xcode upload-dsyms` shipped in 0.7.7 but appeared only in a release-note bullet, and `--concurrency` / `--allow-empty` were nowhere. - **xcode**: the page now covers both commands, opening with a table of which one to run from where. The new `xcode upload-dsyms` section documents the build-phase invocation, the deliberately asymmetric failure policy (a genuine failure fails the build; nothing-to-upload does not), the independent fail/detach pairs and why `--fail --background` is refused, and the Xcode 15 `ENABLE_USER_SCRIPT_SANDBOXING` trap. - **debug-files**: `pdb` moved out of the not-yet-processed list (it works), and `rust` and `il2cpp-linemap` gained table rows and sections of their own — including the Cargo profile settings without which a Rust upload is accepted and then resolves nothing. Documents the new flags, that a missing path is now an error even when other paths hold symbols, and that an already-uploaded symbol is a skip rather than a failure. - **sourcemaps**: concurrency (with the ceiling's scaling rule and why the default is modest), `--allow-empty`, a what-fails-when table, and the foreign-debug-ID registration from 0.7.9. It also warns that `inject` only rewrites `.js`, `.cjs` and `.mjs`: React Native's default `main.jsbundle` is skipped SILENTLY — `js_injected=0`, exit 0 — and the failure only surfaces later as a map with no debug ID. Verified against a binary built from bugsee-cli main at 0.7.10. - **installation**: Windows ARM64 has been published since 0.7.7, so the "only 64-bit x86_64 Windows" line was wrong. Adds the `@bugsee/bugsee-cli` channel and when to prefer `@bugsee/cli` over it. - **release notes**: 0.7.9 and 0.7.10. Behavioural claims were run against that binary, not taken from the changelog. cspell clean; `npm run build` passes with no broken-link or anchor warnings. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> Change-Id: I17dc7e415d9958e6709c3d292f19ec521d317696
krassx
added a commit
to bugsee/bugsee-for-ai
that referenced
this pull request
Sep 19, 2026
`bugsee-upload-symbols` was the only skill that knew about `bugsee-cli`, and it knew it as `@bugsee/bugsee-cli@0.7.5` doing source maps for React Native. Five releases have landed since, including a new command, and no SDK skill mentioned symbols at all beyond a docs link. Adds `skills/bugsee-cli` as the command and contract reference — install channels (including why `@bugsee/cli` beats `@bugsee/bugsee-cli`), the command map, the exit-code contract, the stdout/stderr rule, and the version floors integrators activate against: `xcode upload-dsyms` 0.7.7, duplicate-symbol re-upload 0.7.8, foreign debug-id registration 0.7.9, `--concurrency` / `--allow-empty` 0.7.10. Extends `bugsee-upload-symbols` from "React Native source maps" to every platform, and gives every SDK skill a Debug Symbols section — React Native, Unity and Cordova said nothing about symbols at all. The existing Verify section is kept as-is: its five MCP-driven steps are better than what this change would otherwise have written. The pin discipline is kept too, moved to 0.7.10 and to `@bugsee/cli`, and `bugsee-sourcemaps` stays a `react-native-bugsee` devDependency rather than an unpinned global install. Two things worth calling out, both verified against a binary built from the CLI's main at 0.7.10 rather than taken from a changelog: - `sourcemaps inject` only rewrites `.js`, `.cjs` and `.mjs`. React Native's default `main.jsbundle` is skipped SILENTLY (`js_injected=0`, exit 0) and the failure only surfaces at upload time as a map with no debug ID. So RN keeps `bugsee-sourcemaps` as its documented path, and the trap is written down in all three places that could lead someone into it. - The docs site trailed the binary for `xcode upload-dsyms`, `--concurrency` and `--allow-empty`. bugsee/docs#65 fixes that; skills link only to pages that exist and say `--help` is authoritative for an installed version. Every command, flag and exit code here was checked against that binary; behavioural claims (exit 10 / 0 on empty, 10 on a missing path, 20 for a misapplied flag, 2 for the refused fail+detach pair) were run, not assumed. Plugin manifests go to 1.4.0 for the new skill. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
krassx
added a commit
to bugsee/bugsee-for-ai
that referenced
this pull request
Sep 23, 2026
`bugsee-upload-symbols` was the only skill that knew about `bugsee-cli`, and it knew it as `@bugsee/bugsee-cli@0.7.5` doing source maps for React Native. Five releases have landed since, including a new command, and no SDK skill mentioned symbols at all beyond a docs link. Adds `skills/bugsee-cli` as the command and contract reference — install channels (including why `@bugsee/cli` beats `@bugsee/bugsee-cli`), the command map, the exit-code contract, the stdout/stderr rule, and the version floors integrators activate against: `xcode upload-dsyms` 0.7.7, duplicate-symbol re-upload 0.7.8, foreign debug-id registration 0.7.9, `--concurrency` / `--allow-empty` 0.7.10. Extends `bugsee-upload-symbols` from "React Native source maps" to every platform, and gives every SDK skill a Debug Symbols section — React Native, Unity and Cordova said nothing about symbols at all. The existing Verify section is kept as-is: its five MCP-driven steps are better than what this change would otherwise have written. The pin discipline is kept too, moved to 0.7.10 and to `@bugsee/cli`, and `bugsee-sourcemaps` stays a `react-native-bugsee` devDependency rather than an unpinned global install. Two things worth calling out, both verified against a binary built from the CLI's main at 0.7.10 rather than taken from a changelog: - `sourcemaps inject` only rewrites `.js`, `.cjs` and `.mjs`. React Native's default `main.jsbundle` is skipped SILENTLY (`js_injected=0`, exit 0) and the failure only surfaces at upload time as a map with no debug ID. So RN keeps `bugsee-sourcemaps` as its documented path, and the trap is written down in all three places that could lead someone into it. - The docs site trailed the binary for `xcode upload-dsyms`, `--concurrency` and `--allow-empty`. bugsee/docs#65 fixes that; skills link only to pages that exist and say `--help` is authoritative for an installed version. Every command, flag and exit code here was checked against that binary; behavioural claims (exit 10 / 0 on empty, 10 on a missing path, 20 for a misapplied flag, 2 for the refused fail+detach pair) were run, not assumed. Plugin manifests go to 1.4.0 for the new skill. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The CLI docs stopped at 0.7.8 in the release notes and, in the reference pages, at 0.7.6.
xcode upload-dsymsshipped in 0.7.7 but existed only as a release-note bullet —/cli/xcode/never documented it — and--concurrency/--allow-emptyappeared nowhere.installation.mdstill said only 64-bit x86_64 Windows was published, which stopped being true in 0.7.7.What changed
xcode.md— the page now covers both commands, opening with a table of which to run from where. The newxcode upload-dsymssection documents the build-phase invocation, the deliberately asymmetric failure policy (a genuine failure fails the build; nothing-to-upload does not), the independent fail/detach pairs and why--fail --backgroundis refused, and the Xcode 15ENABLE_USER_SCRIPT_SANDBOXINGtrap.debug-files.md—pdbmoved out of the not-yet-processed list (it works), andrustandil2cpp-linemapgained table rows and sections of their own, including the Cargo profile settings without which a Rust upload is accepted and then resolves nothing. Adds the new flags, the missing-path-is-an-error change, and that an already-uploaded symbol is a skip rather than a failure.sourcemaps.md— concurrency (with the ceiling's scaling rule and why the default is modest),--allow-empty, a what-fails-when table, and the foreign-debug-ID registration from 0.7.9.installation.md— Windows ARM64, the@bugsee/bugsee-clichannel, and when to prefer@bugsee/cli.release-notes.md— 0.7.9 and 0.7.10. Plusindex.mdxandcommands.mdrows, and three terms added tocspell.json.One thing worth a look
This is now a
:::warningon the source maps page. It was found by running a binary built frombugsee-climainat 0.7.10, not by reading the changelog. If the CLI is meant to be React Native's source-map path,injectshould probably recognise.jsbundle— a CLI-side fix that would let this warning be deleted.Verification
--help; behavioural claims run, not assumednpx cspellclean across the sectionnpm run buildpasses with no broken-link or anchor warnings; all five new anchors confirmed present in the built HTMLNote on branching
.claude/CLAUDE.mdsays to work onmainand push there directly. This went to a branch and a PR instead, since recent history shows PRs in use (#64) and a push tomainauto-deploys to production. Merge whenever you're happy with it — or say the word and I'll push straight tomainnext time.🤖 Generated with Claude Code