chore(js): bump versions for packages with unreleased changes

[kixelated]

Summary

The JS release workflow publishes each package's current package.json version on push to main, skipping any version already on the registry. Several packages have had source changes merged since their currently published version, so their next release would be skipped as "already published" and the merged work would never ship.

This bumps the patch version for each package whose published version already matches main but whose src/ has changed since the last release:

Package	Bump	Notable change since release
@moq/net	0.1.5 → 0.1.6	Group.state encapsulation, refactors
@moq/hang	0.2.11 → 0.2.12	compressed catalog track (catalog.json.z)
@moq/watch	0.2.17 → 0.2.18	HLS routing, compressed catalog
@moq/publish	0.2.15 → 0.2.16	new public CATALOG_TRACK_COMPRESSED
@moq/json	0.1.0 → 0.1.1	group roll refactor
@moq/msf	0.1.2 → 0.1.3	moq-mux backport
@moq/signals	0.1.9 → 0.1.10	CreateOptions type fix
@moq/boy	0.2.10 → 0.2.11	source updates

Patch increments follow the repo's established cadence (the last bump in #1846 was patch-level across the board).

Left unchanged

• @moq/loc, @moq/token: only a devDependency (TypeScript) changed, no src/ change, so the published artifact is unaffected.
• @moq/clock: "private": true, never published.
• @moq/flate: at 0.1.0 but not yet on npm/JSR. Its first release is still pending and it has no changes, so it stays at 0.1.0.

Test plan

• All eight edited package.json files remain valid JSON.
• Diff is exactly the eight version lines, nothing else.
• bun install --frozen-lockfile validates the lockfile (internal deps use workspace:*/workspace:^, so no lockfile regen needed). Full just check could not run in this environment because a native dependency's postinstall needs git access that the sandbox blocks; this is unrelated to the version-only change.

🤖 Generated with Claude Code

(Written by Claude Opus 4.8)

---

Generated by Claude Code

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9af0348d-2299-4e76-b55a-40d422968985

📥 Commits

Reviewing files that changed from the base of the PR and between 6bcedb4 and 3c1eeef.

📒 Files selected for processing (8)

• js/hang/package.json
• js/json/package.json
• js/moq-boy/package.json
• js/msf/package.json
• js/net/package.json
• js/publish/package.json
• js/signals/package.json
• js/watch/package.json

---

Walkthrough

Eight package.json files in the js/ directory each have their version field incremented by one patch version: hang 0.2.11→0.2.12, json 0.1.0→0.1.1, moq-boy 0.2.10→0.2.11, msf 0.1.2→0.1.3, net 0.1.5→0.1.6, publish 0.2.15→0.2.16, signals 0.1.9→0.1.10, and watch 0.2.17→0.2.18. No other fields were changed in any of these files.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly states the main change: patch version bumps for packages with unreleased changes.
Description check	✅ Passed	The description directly explains the version bumps and why they were needed, matching the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch claude/bump-js-package-versions-tp30wi

---

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

_{Comment @coderabbitai help to get the list of available commands.}