Skip to content

chore(js): bump @moq/publish to 0.5.6 on release - #8213

Merged
kixelated merged 1 commit into
releasefrom
backport/publish-0.5.6
Nov 7, 2026
Merged

kixelated merged 1 commit into
releasefrom
backport/publish-0.5.6

Conversation

@kixelated

Copy link
Copy Markdown
Collaborator

Problem

moq-dev/moq#8118 (rolls audio groups before the per-group cap) merged into release as c4c4078 but is unpublished; @moq/publish is still 0.5.5.

Approach

Bump @moq/publish 0.5.5 -> 0.5.6 in js/publish/package.json and bun.lock, matching the 0.5.5 bump (396fd3e). The maintainer chose the patch level.

Impact

  • Public API: none
  • Wire: none

Alternatives

None.

Follow-ups

None. Local bun install --frozen-lockfile and bun run check in js/publish pass.

Models

  • Size: XS
  • Implementer: Claude Code, claude-opus-5-5, effort high

Review

Skipped: trivial version bump.

🤖 Generated with Claude Code

(Written by Claude Opus 5.5 with high)

Ships the audio group roll backport (#8118, c4c4078), which rolls
audio groups before the per-group cap. Patch level chosen by the
maintainer.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes

  • @moq/publish version bump (js/publish/package.json): 0.5.5 to 0.5.6, the release-side bump that ships the already-merged #8118 audio group cap fix (c4c407829).
  • Lockfile sync (bun.lock): matching workspace version entry, the only place the JS version is duplicated per CONTRIBUTING.md.

Verified: release is on 0.5.5, npm latest is 0.5.5 (so 0.5.6 is genuinely unpublished and js/common/release.ts will publish rather than skip), the package's @moq/* dependency ranges still point at published versions (hang 0.5.4, json 0.4.3, net 0.4.7, signals 0.2.6), and every in-repo consumer uses the workspace: protocol. bun install --frozen-lockfile resolves against the updated lock. The patch level matches the fix(publish) nature of the shipped change and the precedent of 396fd3e67.

(Written by DeepSeek V4.1 Flash 1017)

Pullfrog  | View workflow run | Using deepseek-v4.1-flash-1017 (free via Pullfrog for OSS) | 𝕏

@kixelated kixelated left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated review by review (OpenAI)

Reviewed head 558e6a6 against release base 9e53401. No actionable findings in the two-file version bump.

package.json and bun.lock consistently move @moq/publish from 0.5.5 to 0.5.6, and GitHub confirms the target base descends from the cited audio-group-cap fix c4c4078. The patch bump is consistent with releasing that existing fix.

Verification limits: GitHub-only diff, ancestry and review inspection. No install, package checks or registry verification run; this review does not publish the package. Rechecked state, full head/base and reviews immediately before posting.

@kixelated
kixelated merged commit a2e6e1c into release Nov 7, 2026
20 checks passed
@kixelated
kixelated deleted the backport/publish-0.5.6 branch November 7, 2026 23:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant