Release v0.47.0 - #181
Merged
Merged
Release v0.47.0#181
Conversation
A minor bump: every workspace module, its intra-workspace dependency pins, `bit_version_tag` and `npm/package.json` move from 0.46.4 to 0.47.0 together, the way the previous releases did. Since v0.46.4, `main` gained new capability rather than fixes alone, which is what makes this a minor and not a patch: - `bit serve --http`, a real listener for the Git smart protocol over many repositories (#178), with protocol v2 `ls-refs` on the upload-pack side and side-band-64k framing on receive-pack. - The object-storage layer underneath it: `bit_objstore` with compare-and-swap writes, a write-ahead log over it, and an S3 transport plus response headers and DELETE in `bit_io_native`. - The toolchain move to MoonBit 0.10.13 / moonbitlang/async 0.22 with every third-party dependency at its latest release (#179), which changed the npm CLI payload to an ES module. - A deprecation-free tree: `moon check` now reports no warnings on native, js or wasm (#180). `moon check` passes for native, js and wasm after the bump — the intra-workspace pins resolve consistently — and the JS build reports `git version 2.47.0 (bit v0.47.0)`. Publishing is left to the maintainer. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0134zgvUroAxAAggLS9yufPX
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A minor bump, 0.46.4 → 0.47.0. One commit moves every version in the workspace together, the same set the previous release commits touched:
versionin all 45modules/*/moon.mod, plus their intra-workspace dependency pins ("mizchi/bit_core@0.47.0"and friends) — 254 references in 47 files.bit_version_taginmodules/bit/cmd/bit/version.mbt→"2.47.0 (bit v0.47.0)". The leading2.47.0is the git version bit reports for compatibility and stays put.npm/package.json→0.47.0.component/moon.mod.json(0.2.0, and it depends onmizchi/bitby path, so it carries no pin) and the rootpackage.json(0.34.0) are out of scope, as in every previous release.Why minor rather than patch
maingained capability since v0.46.4, not just fixes:bit serve --http(Scalable Git server: phases 0–2 (HTTP listener, object store, WAL) #178) — a real listener for the Git smart protocol serving many repositories, with protocol v2ls-refson upload-pack and side-band-64k framing on receive-pack.bit_objstorewith compare-and-swap writes, a write-ahead log over it, and an S3 transport plus response headers andDELETEinbit_io_native.npm/bit.mjs, re-exported bynpm/bit.js).moon checkreports no warnings on native, js or wasm.Verification
moon checkfor native, js and wasm: 0 errors, 0 warnings each, which is also the check that the bumped intra-workspace pins still resolve against the local modules rather than the registry.moon build --target js --release modules/bit, thennode bit.js --version→git version 2.47.0 (bit v0.47.0).node --test tools/module-publish-graph.test.mjs tools/publish-moon.test.mjs tools/publish-changed.test.mjs tools/taskfile.test.mjs: 5/7. The two failures arespawnSync("pkf", ..)returningstatus: null— thepkfCLI is not installed in the sandbox this was prepared in, so the calls never ran. CI installs pkfire/pkspec, so they run there.Left to the maintainer
Publishing is deliberately not part of this PR:
pkf run publish-moon(orpublish-changed-apply) for the Moon modules,pkf run release-npmfor the npm package, and thev0.47.0tag.🤖 Generated with Claude Code
https://claude.ai/code/session_0134zgvUroAxAAggLS9yufPX
Generated by Claude Code