Handoff — 2026-09-19 — Rickub migration and the Release workflow

State

Module rickub.com/turbo-editors/turbo-moonbit, pinned to rickub.com/turbo-editors/turbo-core v1.0.0; GOWORK=off make check green.
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.
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.

Next steps

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.
Watch the Release workflow on the Actions tab. turbo-go's identical workflow has run and published; this one has not yet.
If the publish step answers 403, the binaries are on the run page as the turbo-moonbit-<tag> artifact (14 days).
turbo-moonbit.token.env was deleted on 2026-09-19; nothing read it any more.

Traps

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.
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.
release/ holds the Codeberg-era binaries (hundreds of MB). Gitignored; the tests skip it when copying the module.
sed -i on this filesystem drops the execute bit; chmod 755 the scripts after any such edit.

Later the same day — blocked on turbo-core v1.0.1

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.

Blocked on turbo-core v1.0.2 now

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.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29


# Handoff — 2026-09-19 — Rickub migration and the Release workflow

## State

- Module `rickub.com/turbo-editors/turbo-moonbit`, pinned to `rickub.com/turbo-editors/turbo-core v1.0.0`; `GOWORK=off make check` green.
- 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.
- **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.

## Next steps

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.
2. Watch the Release workflow on the Actions tab. turbo-go's identical workflow has run and published; this one has not yet.
3. If the publish step answers 403, the binaries are on the run page as the `turbo-moonbit-<tag>` artifact (14 days).
4. `turbo-moonbit.token.env` was deleted on 2026-09-19; nothing read it any more.

## Traps

- `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.
- 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.
- `release/` holds the Codeberg-era binaries (hundreds of MB). Gitignored; the tests skip it when copying the module.
- `sed -i` on this filesystem drops the execute bit; `chmod 755` the scripts after any such edit.

## Later the same day — blocked on turbo-core v1.0.1

`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.

## Blocked on turbo-core v1.0.2 now

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.