| 📦 Turbo MoonBit cc1f595 k33g 23h ago | 1 | # Handoff — 2026-09-19 — Rickub migration and the Release workflow |
| 2 | |
| 3 | ## State |
| 4 | |
| 5 | - Module `rickub.com/turbo-editors/turbo-moonbit`, pinned to `rickub.com/turbo-editors/turbo-core v1.0.0`; `GOWORK=off make check` green. |
| 6 | - Releases: `./01-release.tag.sh` tags; the tag push runs `.github/workflows/release.yml`, which builds with `./02-build-releases.sh` and publishes the page with the binaries. `02-release.publish.sh` and `04-release.upload-binaries.sh` are deleted. No token needed. |
| 7 | - **Nothing is committed.** Fresh `git init`, `origin` at `ssh://git@rickub.com/turbo-editors/turbo-moonbit.git`, no commit; the sandbox cannot reach the remote. |
| 8 | |
| 9 | ## Next steps |
| 10 | |
| 11 | 1. Check `release.env` (`TAG="v1.0.0"`, `ABOUT="Turbo MoonBit"`) and run `./01-release.tag.sh` from a machine that reaches Rickub. It makes the root commit, pushes `main`, tags, pushes the tag. |
| 12 | 2. Watch the Release workflow on the Actions tab. turbo-go's identical workflow has run and published; this one has not yet. |
| 13 | 3. If the publish step answers 403, the binaries are on the run page as the `turbo-moonbit-<tag>` artifact (14 days). |
| 14 | 4. `turbo-moonbit.token.env` was deleted on 2026-09-19; nothing read it any more. |
| 15 | |
| 16 | ## Traps |
| 17 | |
| 18 | - `go.work` beside this checkout (where there is one) points at `../turbo-core`. Check the *published* shape with `GOWORK=off`; the release tests already do for their children. |
| 19 | - Do not `go get …/turbo-core@v0.9.0` under the new path: the proxy has it, but its `go.mod` declares the Codeberg path. v1.0.0 is the first usable version. |
| 20 | - `release/` holds the Codeberg-era binaries (hundreds of MB). Gitignored; the tests skip it when copying the module. |
| 21 | - `sed -i` on this filesystem drops the execute bit; `chmod 755` the scripts after any such edit. |
| 22 | |
| 23 | ## Later the same day — blocked on turbo-core v1.0.1 |
| 24 | |
| 25 | `make check` fails on macOS against turbo-core v1.0.0 (see `history.md`: symlinked temp dirs and moon-lsp). Wait for turbo-core v1.0.1, re-pin (`go get rickub.com/turbo-editors/turbo-core@v1.0.1 && go mod tidy && GOWORK=off make check`), then release. The MoonBit toolchain 2026-09-15 is installed in the sandbox (`~/.moon/bin`), so the real-server tests run here now. |
| 26 | |
| 27 | ## Blocked on turbo-core v1.0.2 now |
| 28 | |
| 29 | v1.0.1 fixed the symlink failures; the next `make check` on the Mac hit the "never diagnosed after start" pin, which is a turbo-core limit fixed in v1.0.2 (see `history.md`). Re-pin to v1.0.2, `GOWORK=off make check`, release. |