chore(release): 0.7.13

[krassx]

Ships what landed since 0.7.12:

• chore: license under MIT #67 — MIT license: LICENSE, crate license, and license + LICENSE in all eight npm packages, the release archives and the Homebrew formula.
• docs: validate READMEs against the code and published 0.7.12 #65 — the corrected npm/cli/README.md reaches the @bugsee/cli npm page (npm only takes a README from a published version).
• fix(build-env): machine-label hostname fallback was empty on macOS #66 — build-env machine-label hostname fallback on macOS / Windows.

Version bump in Cargo.toml / Cargo.lock, changelog dated. dist plan --tag v0.7.13: same 6 build targets as 0.7.12.

After merge: tag v0.7.13 → release.yml → npm-publish.yml + mirror-to-s3.yml.

🤖 Generated with Claude Code

[cursor]

Reviewed this as a release PR, not a 10-line diff. Intent is to ship everything since v0.7.12 as 0.7.13: #65 (docs / @bugsee/cli README), #66 (build-env machine-label hostname fallback), #67 (MIT on the crate and published artefacts). After merge the next step is still tag v0.7.13 → release.yml → npm-publish.yml + mirror-to-s3.yml.

Checked against git v0.7.12..HEAD, the shipping code for those three PRs, Cargo.toml/Cargo.lock/clap --version, npm stamping (0.0.0-dev template + npm/build.mjs crate version), and the 0.7.12 changelog/release-notes shape cargo-dist already parsed successfully. Ran local_hostname_resolves_on_unix, no_provider_returns_local_hostname_or_none, and payload_builder_shape_matches_agent; bugsee-cli --version prints bugsee-cli 0.7.13.

Findings

No P0–P3 issues. Nothing in this bump looks like it would mis-tag, mis-announce, or ship a broken artefact.

• Changelog vs git: [Unreleased] is empty; ## [0.7.13] - 2026-10-07 contains MIT (#67), the npm README correction (#65, added here because #65 itself had no Unreleased bullet), and the macOS/Windows hostname fix (#66). Those are the only three commits since v0.7.12. Patch bump is the right SemVer (no wire/CLI break).
• Version single source of truth: Cargo.toml, Cargo.lock, cargo metadata, and the built binary all say 0.7.13. npm/cli/package.json staying at 0.0.0-dev is correct — build.mjs stamps the crate version at publish. Dist still has the same six targets; plugin_version is concat!("bugsee-cli/", env!("CARGO_PKG_VERSION")), so registration metadata will follow.
• Code being shipped: #66 reads hostname via gethostname(2) / COMPUTERNAME instead of /usr/bin/hostname, which is what actually fills build_metadata.machine on a local xcode post-action. #67 puts LICENSE + license = "MIT" on the crate, cargo-dist archives/Homebrew/@bugsee/bugsee-cli, and the seven @bugsee/cli* packages. I did not re-litigate those already-merged PRs into new findings.

Leaving npm/README.md on gh release download v0.7.12 is the right call until 0.7.13 assets exist; pointing that recipe at this tag now would 404.

Verdict

1. Overall risk: Low
2. Merge recommendation: Approve. Merge, then tag v0.7.13 on the merge commit (same path as 0.7.12).
3. Most important issues to fix: None.
4. Positives: Tight release hygiene — version + dated notes only, #65 backfilled instead of silently omitted, same Keep-a-Changelog / empty-Unreleased shape that produced the 0.7.12 GitHub release notes.

  

_{Sent by Cursor Automation: Bugsee code review}