Repository navigation
Releases: python123-ops/moondepsolve
Release list
MoonDepSolve v0.4.0 — Mooncakes namespace migration
MoonDepSolve 0.4.0 moves the maintained Mooncakes module to python123-ops/moondepsolve and includes all compatibility and version-parsing fixes from 0.3.2.
Install and migrate
moon add python123-ops/moondepsolve@0.4.0Replace python123/moondepsolve with python123-ops/moondepsolve in your package imports and remove the old dependency. The alias remains @moondepsolve; library API names and behavior are otherwise unchanged from 0.3.2. The old python123/moondepsolve@0.3.1 package and previous GitHub tags retain their original namespace.
Validation
- Pinned MoonBit 0.10.19+97801ee1b with moonbitlang/async 0.22.7.
- 35 tests each on wasm, wasm-gc, and js; 39 on native.
- Four exact CLI outputs and three error cases pass.
- The 31-file release archive compiles on all four backends after extraction.
Published
Mooncakes publication succeeded with HTTP 200. The module was then installed from the registry in an independent consumer project; import and public API checks pass on wasm, wasm-gc, js, and native.
Package documentation: https://mooncakes.io/docs/python123-ops/moondepsolve@0.4.0
Linux and Windows CI: https://github.com/python123-ops/moondepsolve/actions/runs/41440791623
MoonDepSolve v0.3.2
Namespace migration
The maintained Mooncakes package is now python123-ops/moondepsolve@0.4.0, published successfully on 2026-11-02. See v0.4.0 for the updated installation and import paths. The v0.3.2 source tag below retains the original namespace.
MoonDepSolve 0.3.2 updates the project for MoonBit 0.10.19+97801ee1b and moonbitlang/async 0.22.7.
- Preserve existing equality method calls through explicit extensions, remove deprecated implicit promotion, and refresh executable manifests and generated interfaces.
- Fix overflowing version numbers and range bounds, leading zeroes, malformed prereleases, large numeric prerelease ordering, and requirements with x in prerelease names.
- Add Linux/Windows CI with a pinned compiler, all stable backends, cross-platform CLI checks, and extracted-package validation.
- Keep competition documents and site assets out of the 34 KB library archive.
Validation: 35 tests each on wasm, wasm-gc, and js; 39 on native. Four exact CLI outputs and three error cases pass. The packaged sources compile on all four backends after extraction.
Mooncakes status: python123/moondepsolve@0.3.1 remains the published version. Publishing 0.3.2 under that namespace requires authentication as python123; the available python123-ops login is rejected with a namespace mismatch. This GitHub source release does not claim a new Mooncakes publication.
MoonDepSolve v0.3.0
MoonDepSolve v0.3.0
MoonDepSolve v0.3.0 adds exact upgrade planning and a native file-driven CLI while preserving the v0.1/v0.2 public APIs.
Highlights
- Exact
MinimalChangeplanning minimizes changed packages globally, then prefers higher versions for deterministic ties. HighestCompatibleproduces an explicit upgrade plan from the existing resolver.- Structured add/remove/upgrade/downgrade changes and bounded search errors.
- Native
resolveandplancommands read registry/lock files and emit lock, text graph, or Graphviz DOT. - 27 default-backend tests, 31 native tests, and four deterministic CLI output regressions.
- Full-history contributor identity gate for
python123and synchronized GitLink/GitHub delivery.
Compatibility
This release is additive. Existing parsing, matching, resolution, lock, dependency graph, and conflict report APIs remain available.
ConflictReport.package remains unchanged for v0.2 compatibility. Current MoonBit toolchains report that field as warning 35 because package is reserved for possible future use; project checks suppress only that warning.
Verify
moon test --warn-list=-35
moon test --target native --warn-list=-35
sh scripts/demo-v0.3.shLicense: Apache-2.0.