chore(js): bump @moq/net to 0.4.3 on release

[kixelated]

Bumps the release-line @moq/net so the draft-22 backports ship to npm (step from quest/m0/release-22).

Bumps

• @moq/net 0.4.2 → 0.4.3 (patch): fix(net): accept a clear FIRST_OBJECT that starts at object 0 (backport #5027) #5069 (clear FIRST_OBJECT at object 0, backport fix(net): accept a clear FIRST_OBJECT that starts at object 0 #5027) and fix(net): draft-22 LOCATION_FILTER carries its Location Filter Type (backport #5080) #5094 (draft-22 LOCATION_FILTER, backport fix(net): draft-22 LOCATION_FILTER carries its Location Filter Type #5080) changed js/net since 0.4.2.

Examined and left alone

• Rust crates: release-plz owns them (chore: release #4944 regenerates for 0.17.3).
• @moq/flate: only dependency and publish-script changes since 0.1.3.
• Other JS packages: no changes since their last bump (chore(js): bump unpublished release packages #4795).
• Swift 0.5.1, Dart 0.1.0, Kotlin 0.5.1, Python moq-rs 0.5.1: the published artifacts differ from release only in doc comments.
• Go: no breaking change, so go/wrapper/VERSION stays; CI derives the patch.

API / wire impact

None; version metadata only.

Note

If more JS backports land on release (e.g. #5019), merge this after them so 0.4.3 carries them, or bump again.

(Written by Claude Opus 5.5)

🤖 Generated with Claude Code

[chatgpt-codex-connector]

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-09T21:47:45.511505Z	25dc8e7	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]

Automated review of 25dc8e7d

This is a version-only patch bump (@moq/net 0.4.2 → 0.4.3 in js/net/package.json and bun.lock). I checked the claims: #5069 and #5094 both merged into release and touch js/net, and npm's latest is 0.4.2, so 0.4.3 is unpublished and a patch bump is the right size. I found no issues.

Non-blocking:

• As the body says, fix(js): drop a headless subgroup before FIRST_OBJECT #5019 merged to main and also touches js/net/src/ietf/{object,subscriber}.ts. If it gets backported to release, land it before this PR or bump again.
• CI was still pending when I reviewed.

Verdict: MERGE

This is an automated review, not the maintainer's decision
(Written by Grok)

[kixelated]

Automated review by review (OpenAI)

Reviewed commit: 25dc8e7

No actionable findings in the full two-file diff. js/net/package.json:4 and bun.lock:229 consistently set @moq/net to 0.4.3. The existing packaging code derives npm/JSR manifests and workspace dependency versions from package.json, so this is an appropriately minimal release bump; no additional mechanism is needed. This diff introduces no runtime, public API, wire-format, or security behavior changes.

Verification: GitHub-only static review of the diff, manifests, packaging/release scripts, and CI configuration. I did not run builds/tests or independently query package registries. Check, Test, and Release JS Packages were still running. Rechecked immediately before posting: open, non-draft, unchanged head, and no existing review submissions.