Merge StarForth-v4.0.0 into master #19

New Issue

2026-11-06T16:01:23Z

rajames commented

2026-11-06 16:01:23 +00:00

master is 295 commits behind the working branch. Expect conflicts: master edits Makefile.starkernel (gone on the branch, now kernel/Makefile) and adds mk/boards.mk; the board names differ (T=qemu|pc|pi4|pi5|milkv against TARGET=PC|RASPI|MILKV|ZYNQ7020). The merge also clears master's 23 log files that are in LFS by .gitattributes but committed as plain files (fixed on the branch in 027b144e). After it, nightly.yml no longer needs to name the branch, and .claude/CLAUDE.md's "works directly on master" is true again.

master is 295 commits behind the working branch. Expect conflicts: master edits `Makefile.starkernel` (gone on the branch, now `kernel/Makefile`) and adds `mk/boards.mk`; the board names differ (`T=qemu|pc|pi4|pi5|milkv` against `TARGET=PC|RASPI|MILKV|ZYNQ7020`). The merge also clears master's 23 log files that are in LFS by `.gitattributes` but committed as plain files (fixed on the branch in 027b144e). After it, `nightly.yml` no longer needs to name the branch, and `.claude/CLAUDE.md`'s "works directly on master" is true again.

rajames added the

labels 2026-11-06 16:01:23 +00:00

rajames referenced a pull request that will close this issue

2026-11-06 16:05:30 +00:00

Merge StarForth-v4.0.0 into master #30

rajames referenced this issue from a commit

2026-11-06 18:58:02 +00:00

Merge StarForth-v4.0.0 into master (#30)