[krassx]

Version bump for the next beta (node scripts/bump-version.mjs 0.1.0-beta.5).

Since beta.4: streaming report export + replay window fix (#173), dialog footer sizing (#172), Electron pixel video as MP4 (#174), async-origin design doc (#175), Astro relaunch/hydration fixes (#178, #179).

After merge: scripts/release.sh --tag beta.

🤖 Generated with Claude Code

[claude]

Claude finished @krassx's task in 14s —— View job

---

Review of #180: chore(release): 0.1.0-beta.5

I found no issues in this version bump.

What I checked

• The diff changes 51 files. It makes 50 package.json edits of 0.1.0-beta.4 → 0.1.0-beta.5, plus the BUGSEE_SDK_VERSION constant in packages/core/src/carrier.ts. Nothing else changes.
• I ran node scripts/check-publishable.mjs, the same consistency check CI runs. It reported "50 publishable packages, all at 0.1.0-beta.5".
• The six packages without the new version are all "private": true (astro-e2e, e2e-kit, instrumentation-tests, nextjs-e2e, nuxt-e2e, sveltekit-e2e). They are meant to be excluded.
• No 0.1.0-beta.4 string remains anywhere in the repo outside node_modules and .git. That rules out hard-coded versions in tests, docs or snapshots.
• I found no inter-package workspace: specifiers that would be affected by the bump.
• I did not run the test suite or the full CI gates. This change is mechanical, and CI will cover them.

Summary

1. Overall risk: Low.
2. Merge recommendation: Approve. I can't approve PRs myself, so this is a recommendation only. Wait for CI to pass, then run scripts/release.sh --tag beta as the description says.
3. Issues to fix: None.
4. Positives: The bump was generated by the repo's own script, and check-publishable enforces that the SDK constant and every package version stay in sync. The PR description lists what changed since beta.4.

[coderabbitai]

Caution

Review failed

The pull request is closed.

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

CodeRabbit Verify

• Run CodeRabbit Verify to test the changes in this pull request.

[cursor]

Version bump is complete and internally consistent. No P0–P3 in this diff.

What this PR does: node scripts/bump-version.mjs 0.1.0-beta.5 — the same 51-file shape as beta.4 (#169): every publishable package.json plus BUGSEE_SDK_VERSION in packages/core/src/carrier.ts (the value the SDK reports to the collector and the carrier slot key).

What I checked against surrounding release machinery, not just the diff:

• scripts/check-publishable.mjs / loadPackages(): 50 publishable packages, all at 0.1.0-beta.5. The six unbumped packages (astro-e2e, e2e-kit, instrumentation-tests, nextjs-e2e, nuxt-e2e, sveltekit-e2e) are private test harnesses and are excluded by design.
• @bugsee/packaging-guard sdk-version.test.ts: 13 passed (reported version matches package versions; launch files import the constant rather than hardcoding it).
• No leftover 0.1.0-beta.4 in source. Inter-package deps are workspace:*, rewritten to the packed version at publish (scripts/publish-all.mjs); the lockfile did not need a version rewrite.
• Package set is unchanged since beta.4; sampled names already exist on npm at 0.1.0-beta.4, so this release should not need the first-publish bootstrap path.
• BUGSEE_SDK_VERSION is the carrier slot key on purpose: mixed beta.4 and beta.5 copies in one process get separate interceptor slots (documented coexistence trade-off, not a regression).

This PR was merged to main as 5037d0f while the review was in progress. The bump itself is safe to ship. scripts/release.sh will still wait for CI green on that SHA.

Findings

None in the version bump.

Overall

1. Overall risk: Low
2. Merge recommendation: Already merged. The bump is correct; no follow-up commit needed for version consistency.
3. Most important issues to fix: None in code. Post-merge operational caution: the PR body says scripts/release.sh --tag beta. The registry currently has only dist-tags.latest = 0.1.0-beta.4 (no beta tag). Previous betas were published onto latest. --tag beta would publish 0.1.0-beta.5 under beta and leave npm install @bugsee/bugsee (and @latest) on beta.4. Use the default (latest) unless splitting the beta tag off latest is intentional.
4. Positives: Generated by the repo's one bump script; CI's pnpm check:publishable is the same invariant the release workflow re-checks before publish. Private harnesses were correctly left alone.

Residual (already on main, not this diff): this version ships #175/#176 async-origin capture (default-on) and #174 Electron pixel video as MP4. Prior review of #175 recorded a wrap-leak on failed/overlapping launch(); that is product residual, not a defect of this bump.

  

_{Sent by Cursor Automation: Bugsee code review}