Skip to content

Prepare selective patch releases - #169

Draft
mizchi wants to merge 1 commit into
mainfrom
agent/release-0.46.1
Draft

Prepare selective patch releases#169
mizchi wants to merge 1 commit into
mainfrom
agent/release-0.46.1

Conversation

@mizchi

@mizchi mizchi commented Jul 30, 2026

Copy link
Copy Markdown
Member

Summary

  • add independent patch / minor release preparation for modules changed since the previous release
  • keep publish ordering and the --apply safety gate while syncing npm and CLI metadata only when mizchi/bit changes
  • migrate deprecated MoonBit default, debug representation, hash, and map APIs
  • prepare patch versions for the 14 touched modules (mizchi/bit and mizchi/bitx_hub at 0.46.1; the other affected modules at 0.45.7)

Why

The workspace release helper previously assumed lockstep versions and the current MoonBit toolchain emitted 121 source deprecation warnings plus four warnings from the release helper. Independent version preparation avoids republishing unchanged modules, while the API migrations keep all supported targets warning-free.

Impact

Release preparation now updates only changed package manifests, preserves topological publishing, refuses unsafe dirty-worktree publishing, and keeps the installable npm/CLI version synchronized with mizchi/bit.

Validation

  • moon check --target native
  • moon check --target js
  • moon check --target wasm
  • node --test tools/module-publish-graph.test.mjs tools/publish-changed.test.mjs (9 passed)
  • affected native package tests (682 passed)
  • mizchi/bit/cmd/git-bit native tests (4 passed)
  • mizchi/bit/cmd/bit release native tests (869 passed)
  • node tools/check-layers.mjs
  • moon build --target native --release modules/bit
  • git diff --check

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