| 📦 Turbo Golo d710c1b k33g 19h ago | 1 | # Handoff — 2026-09-19 — Rickub migration and the Release workflow |
| 2 | |
| 3 | ## State |
| 4 | |
| 5 | - Module `rickub.com/turbo-editors/turbo-golo`, 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-golo.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 Golo"`) 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-golo-<tag>` artifact (14 days). |
| 14 | 4. `turbo-golo.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 — the four-question test went red, as designed |
| 24 | |
| 25 | The user's first `./01-release.tag.sh` stopped in `make check`: GoloScript v0.2.0 answers references, implementations and workspace symbols. Tests and docs (EN + FR, nine pages + README + summary) were revised to say the boundary is `typeDefinition` alone; see `history.md`. GoloScript v0.2.0 is installed in the sandbox at `/usr/local/bin/golo`, so the ten `…WithRealGoloLSP` tests now run here instead of skipping. Re-run `./01-release.tag.sh`. |