Skip to content

chore(js): bump @moq/net, hang, publish, and signals on release - #5673

Merged
kixelated merged 1 commit into
releasefrom
bump/release-npm-patch
Oct 17, 2026
Merged

kixelated merged 1 commit into
releasefrom
bump/release-npm-patch

Conversation

@kixelated

Copy link
Copy Markdown
Collaborator

Patch bumps for the release-line JS packages, so the backports merged since the last publish ship to npm. Compared each package against the release commit at its npm publish time.

Bumps

All four are fixes, so patch. The matching workspace versions in bun.lock move with them.

Examined and left alone

  • Rust crates: release-plz owns them (chore: release #5533, merged).
  • @moq/watch, @moq/boy: only the esbuild → rolldown devDependency swap (worklet bundling at build time), so no shipped change.
  • @moq/flate: repository metadata and dependency ranges that already accepted the new versions.
  • Other JS packages: no changes since their last publish.
  • Python, Swift, Kotlin, Go, Dart: no changes on release since chore(js): bump @moq/net to 0.4.3 on release #5119.

Checks

  • just js check and just js test pass locally; bun install --frozen-lockfile accepts the lockfile.

🤖 Generated with Claude Code

(Written by Claude Opus 5.5)

Patch bumps so the release-line backports ship to npm:
@moq/net 0.4.4, @moq/hang 0.5.3, @moq/publish 0.5.3, @moq/signals 0.2.6.

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

chatgpt-codex-connector Bot commented Oct 16, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-16T04:42:40.505707Z 890cb04 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@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 commit: 890cb04.

No actionable bugs found in this release-version change. The four patch versions match bun.lock, and #5582, #5520 and #5448 are ancestors of the release base with their fixes retained. Packaging rewrites workspace dependencies to the new sibling versions, including net → signals ^0.2.6 and publish → hang ^0.5.3. The existing release workflow selects these changes and uses dry-run publishing for PRs. Patch bumps are consistent with the fixes' unchanged signatures and supported wire formats.

Verification: static five-file diff, backport ancestry, dependency packaging and release-workflow review. No tests or packaging executed independently; npm/JSR registry state and historical publish-time baselines were not checked under the GitHub-only scope. Head CI was still running when inspected. This review does not verify publication.

(Written by OpenAI)

@kixelated

Copy link
Copy Markdown
Collaborator Author

Merging: patch bumps @moq/net 0.4.4, @moq/hang 0.5.3, @moq/publish 0.5.3, @moq/signals 0.2.6 on release, with matching bun.lock entries. CI green and the automated review found no issues.

This unblocks moq-dev/smoke: the published @moq/hang 0.5.2 rejects the catalog archive shape the current Rust publisher emits (archive.track expected string), which fails every Rust to JS cell on the nix lane. The #5520 backport shipped here tolerates it.

(Written by Claude Opus 5.5)

@kixelated
kixelated merged commit 0eff2f6 into release Oct 17, 2026
6 checks passed
@kixelated
kixelated deleted the bump/release-npm-patch branch October 17, 2026 17:11
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