Skip to content

chore: rename bobzhang module namespace to moonbitlang, add publish CI - #1350

Open
tonyfettes wants to merge 7 commits into
mainfrom
chore/rename-bobzhang-to-moonbitlang
Open

chore: rename bobzhang module namespace to moonbitlang, add publish CI#1350
tonyfettes wants to merge 7 commits into
mainfrom
chore/rename-bobzhang-to-moonbitlang

Conversation

@tonyfettes

Copy link
Copy Markdown
Contributor

What

Moves every module this repository publishes out of the bobzhang/ owner namespace into moonbitlang/:

  • bobzhang/openseekmoonbitlang/openseek (repo root, moon.mod)
  • bobzhang/openseek_protocolmoonbitlang/openseek_protocol (protocol/)
  • bobzhang/openseek-scriptsmoonbitlang/openseek-scripts (scripts/, unpublished)
  • bobzhang/openseek-viz-appmoonbitlang/openseek-viz-app (cmd/viz_app/, unpublished)
  • bobzhang/inspectmoonbitlang/inspect (inspect/, unpublished)

The rename updates moon.mod name/repository/dependency pins, every moon.pkg import, generated .mbti interface files (moon info), comments/docs, and _build path string literals. Adds a manual CI workflow (.github/workflows/publish-openseek.yml) that publishes moonbitlang/openseek_protocol then moonbitlang/openseek with the org MOONCAKES_MOONBITLANG_TOKEN, plus a root .moonignore so 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.
  • The stale viz/pkg.generated.mbti (a js-only package the current toolchain no longer regenerates via moon info) is deleted rather than left carrying an old bobzhang/openseek/viz header.
  • bobzhang/openseek and bobzhang/openseek_protocol remain published on mooncakes under the old owner; the new moonbitlang/* modules are first published by the new workflow (manual dispatch after this merges).

Verified

  • moon check clean across the workspace (native), moon fmt --check clean, moon info regenerates .mbti without drift.
  • moon test --target native protocol passes (22/22).
  • Full native/js/wasm test matrix not run locally (needs Proton/CEF runtime); CI runs it on this PR.

Generated with SeekMoon

tonyfettes and others added 7 commits September 7, 2026 19:17
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>
@tonyfettes
tonyfettes force-pushed the chore/rename-bobzhang-to-moonbitlang branch from 5fa4c41 to d608191 Compare September 7, 2026 11:21
@tonyfettes
tonyfettes marked this pull request as ready for review September 7, 2026 11:28
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 7, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-07T11:35:31.152337Z d608191 Draft marked ready
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

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