chore: rename bobzhang module namespace to moonbitlang, add publish CI - #1350
chore: rename bobzhang module namespace to moonbitlang, add publish CI#1350tonyfettes wants to merge 7 commits into
Conversation
Adds a manual publish-openseek workflow for the moonbitlang/openseek and moonbitlang/openseek_protocol modules (mirroring publish-editor), and a root .moonignore so publishing the root monorepo module does not bundle the nested member modules. Co-Authored-By: SeekMoon <seekmoon@moonbitlang.com>
Renames the modules published from this repository from the bobzhang/ owner to moonbitlang/ (moonbitlang/openseek, moonbitlang/openseek_protocol, moonbitlang/inspect, moonbitlang/openseek-scripts, moonbitlang/openseek-viz-app): moon.mod name/repository/dependency-pin fields, every moon.pkg import, comments and docs, and build-path string literals. Regenerates the .mbti interface files with moon info; drops the js-only viz/pkg.generated.mbti, which the current toolchain does not regenerate, rather than leaving a stale bobzhang/ header. bobzhang/myshell (a third-party module) is untouched. Co-Authored-By: SeekMoon <seekmoon@moonbitlang.com>
Consumer modules (desktop, cmd/viz_app, inspect) pin moonbitlang/openseek at the version that will actually be published under the new owner (0.3.1). The publish workflow removes the mooncakes credentials file via an EXIT trap as well as after a successful publish, and documents that the secret is the moonbitlang org token. Co-Authored-By: SeekMoon <seekmoon@moonbitlang.com>
5fa4c41 to
d608191
Compare
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d608191190
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| fi | ||
| trap 'rm -f ~/.moon/credentials.json' EXIT | ||
| echo "$SECRET" > ~/.moon/credentials.json | ||
| moon publish |
There was a problem hiding this comment.
Skip publishing an unchanged protocol version
On any later root-only release, which the header explicitly permits by saying to bump moon.mod and/or protocol/moon.mod, this unconditional publish attempts to upload the already-published protocol version before reaching the root step. Mooncakes rejects duplicate package versions, so the job exits here and never publishes the newly versioned root module; make module selection explicit or skip coordinates whose versions are already published.
Useful? React with 👍 / 👎.
What
Moves every module this repository publishes out of the
bobzhang/owner namespace intomoonbitlang/:bobzhang/openseek→moonbitlang/openseek(repo root,moon.mod)bobzhang/openseek_protocol→moonbitlang/openseek_protocol(protocol/)bobzhang/openseek-scripts→moonbitlang/openseek-scripts(scripts/, unpublished)bobzhang/openseek-viz-app→moonbitlang/openseek-viz-app(cmd/viz_app/, unpublished)bobzhang/inspect→moonbitlang/inspect(inspect/, unpublished)The rename updates
moon.modname/repository/dependency pins, everymoon.pkgimport, generated.mbtiinterface files (moon info), comments/docs, and_buildpath string literals. Adds a manual CI workflow (.github/workflows/publish-openseek.yml) that publishesmoonbitlang/openseek_protocolthenmoonbitlang/openseekwith the orgMOONCAKES_MOONBITLANG_TOKEN, plus a root.moonignoreso publishing the monorepo root module does not bundle the nested member modules.Notes / exceptions
bobzhang/myshell(a third-party module used in mbtx sandbox test fixtures) is intentionally untouched.viz/pkg.generated.mbti(a js-only package the current toolchain no longer regenerates viamoon info) is deleted rather than left carrying an oldbobzhang/openseek/vizheader.bobzhang/openseekandbobzhang/openseek_protocolremain published on mooncakes under the old owner; the newmoonbitlang/*modules are first published by the new workflow (manual dispatch after this merges).Verified
moon checkclean across the workspace (native),moon fmt --checkclean,moon inforegenerates.mbtiwithout drift.moon test --target native protocolpasses (22/22).Generated with SeekMoon