chore: bump version to 0.12.0 - #49
Conversation
Releases the X-Wherobots-Client attribution hop fix (#48), which has been on dev since 2026-08-07 and unpublished. npm latest is still 0.11.1. Bumps package.json and both version fields in package-lock.json so the CI lockfile drift check stays green. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Reviewed by Salty Hambot 🤖🧂 — rubric mode
Verdict: ✅ pass
| Dimension | Verdict | Notes |
|---|---|---|
| correctness | ✅ pass | Single semver bump, valid JSON, no logic touched. |
| security | ✅ pass | No dependency or code changes with security impact. |
| privacy | ✅ pass | No data handling changes. |
| reliability | ✅ pass | Version metadata only; no runtime behavior affected. |
| scalability | ✅ pass | No performance-relevant changes. |
| observability | ✅ pass | No logging or metrics changes. |
| clarity/maintainability | ✅ pass | Trivial, self-explanatory version bump. |
| test quality | ✅ pass | No code changes requiring tests. |
Just a version bump from 0.11.1 to 0.12.0 — clean as a whistle, nothing to see here.
0 finding(s) posted.
💰 Review cost: $0.1143 · 32.0k in / 426 out tokens · ⏱️ 17.1s
💬 To request a re-review, comment @salty-hambot review
|
@wherobots/wbc-frontend-crew — review needed on head First review request on this PR; nothing has been dismissed and the code has not moved since it was opened. The only change between draft and now is that I marked it ready and ticked the CI checkbox in the description. Should be a quick one — the diff is 3 lines across 2 files:
No source changes. This cuts the release for the X-Wherobots-Client attribution hop fix (#48), which has been sitting on Two things worth your judgement:
|
|
@zongsizhang i published this to npm |
Summary
Bumps the package version
0.11.1→0.12.0to cut a release. Version bump only — no source changes.0.12.0ships the X-Wherobots-Client attribution hop fix (#48, merged todev2026-08-07 and unpublished since). The SDK had been emitting the legacyX-Wherobots-Client: wherobots-sql-driver/<version>format, which the backend parser records asunknown— so every request from this SDK has been logged as unattributed rather than as a TypeScript SDK request.0.12.0emits a realclient=typescript-sdk;ver=<v>;plat=<p>hop.npm
latestis still0.11.1(published 2026-07-10).Files changed
package.jsonversion:0.11.1→0.12.0package-lock.jsonpackages."") →0.12.0The lockfile carries the version in two places; both are updated so the CI
Check package-lock.json is up to datestep stays green. Verified locally by running that exact step (npm install --package-lock-only --ignore-scripts) — it produces no further changes.Why minor, not patch
Although #48 is prefixed
fix:, it is additive to the public API — it introducedsrc/clientHeader.tsand a new optionalclientChainconnection option (src/schemas.ts) — so a minor bump is the correct level. It is not breaking for consumers: the changed header is outbound-only and advisory, and no SDK API was removed or renamed.Related Issues
Releases #48.
Requester Checklist
src/clientHeader.test.ts(15 tests) ondevVisual Proof
CI on this branch: Passed 1, Failed 0.
Full CI pipeline also reproduced locally before pushing:
Diff is exactly 3 lines across 2 files:
Notes for the reviewer
npm publishis deliberately not automated here and is not part of this PR — it remains a manual step after merge. This repo has no release automation and no release tags.CHANGELOG.mdis intentionally untouched: it is only sporadically maintained (entries exist for0.11.0and0.3.0only;0.4–0.10and0.11.1are all absent), and no previous version-bump commit has updated it. Happy to add a0.12.0entry if you'd prefer to start that habit with this release.