[kixelated]

Cuts @moq/publish 0.5.5 on release, so Release JS publishes the audio groupDuration backport (moq-dev/moq#7290, merged into release unbumped by the 2026-10-30 decision).

The only js/publish change on release since 0.5.4 (moq-dev/moq#7276) is that additive option, so this is a patch. The maintainer authorized the cut and publish in the 2026-11-06 /quest-unblock session. It unblocks moq-dev/moq#7279, which waits on npm view @moq/publish@0.5.5.

Same shape as #7276: js/publish/package.json and the bun.lock workspace entry.

Review

Skipped as trivial: a version bump with a one-line lockfile change, matching #7276.

(Written by Claude Opus 5.5 with high effort)

🤖 Generated with Claude Code

[pullfrog]

✅ No new issues found.

Reviewed changes

• Version bump: js/publish/package.json moves from 0.5.4 to 0.5.5, the only js/publish surface change since the 0.5.4 cut being the additive audio groupDuration backport (bcd6040fd), which is already documented in doc/lib/js/publish.md and reflected in the API reports. Patch is the right level for an additive option on a backport cut.
• Lockfile: the matching js/publish workspace entry in bun.lock is bumped in the same commit, so bun install --frozen-lockfile in release-js.yml stays consistent. No other version site applies: js/publish has "jsr": false (npm only), no MIGRATE.md, and no CHANGELOG.

I also checked the registry: @moq/publish currently tops out at 0.5.4, so 0.5.5 is free and publishing it will not roll the latest dist tag backwards. Its workspace:^ dependency @moq/hang is already published at 0.5.4. Shape matches the prior 0.5.4 cut.

(Written by DeepSeek V4.1 Flash 1017)

  ^{｜ View workflow run ｜ Using deepseek-v4.1-flash-1017 (free via Pullfrog for OSS) ｜ 𝕏}