Skip to content

[Chore] - Publish a mux-runtime version containing BoxedEnum (unblocks dropping the compiler's git patch) #26

Description

@DerekCorniello

Summary

main has runtime changes that are not on crates.io, and Cargo.toml still
says version = "0.5.0" (same as the published release). Everything that
landed with the recursive/collection enum work in muxlang/mux-compiler#309 is
currently reachable only via a git dependency:

Published mux-runtime 0.5.0 has none of these symbols.

Why this matters now

mux-compiler's root Cargo.toml carries a [patch.crates-io] pointing
mux-runtime at this repo's main branch, precisely because the symbols its
codegen emits calls to do not exist in any published version. That patch is a
development stopgap - [patch.crates-io] is ignored for consumers of a
published crate, so it cannot ship. See the companion issue in mux-compiler.

The work

  • Bump version in Cargo.toml (0.6.0 - new public FFI surface, no
    removals).
  • CHANGELOG entry covering BoxedEnum, the enum comparison glue, and
    rc-leak-check.
  • Verify the full feature list still matches what mux-compiler's
    full_runtime_features() parity test expects (that test reads this
    repo's Cargo.toml directly).
  • Publish (maintainer-only step per the release process).

Blocks

Publishing this unblocks dropping the git patch in mux-compiler and pinning a
real version there.


Companion: muxlang/mux-compiler#316.

Metadata

Metadata

Labels

choreCleanup, maintenance, or dependency bumps

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions