Add support for Haiku R1/beta6 - #163
Conversation
Point the Haiku image at the haiku-builder v0.2.0 release, which is the first release that ships an R1/beta6 image, and add R1/beta6 to the CI matrix and the documentation. R1/beta6 has not been released yet, so the hrev used by the uname assertion in the CI matrix is a placeholder and needs to be filled in once it ships. It's marked with a TODO. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NksedEgMiTdqqBmtbmGKhM
R1/beta6 has not been officially released yet, so its image is built from the official test build, hrev59866_53. Use that hrev in the uname assertion, document it, and keep the readme examples on R1/beta5, since that's the latest released version. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NksedEgMiTdqqBmtbmGKhM
The `*` pattern doesn't match a slash, so pushes to branches like `feature/foo` didn't trigger the workflow. `**` matches across path separators. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NksedEgMiTdqqBmtbmGKhM
|
CI status: 4 jobs fail, all of them Haiku ones — The cause is the (a ranged GET against So this is blocked on cross-platform-actions/haiku-builder#3 being merged and tagged The R1/beta6 build itself is running in haiku-builder#3, and that's what actually validates the test-build ISO. Generated by Claude Code |
|
Would be cool to have something working again. The haiku r1beta5 ci jobs using the current c-p-a release are all broken. |
Beta6 doesn't build with the existing Packer template. It takes additional work.
It's difficult for me to do anything when upstream breaks its users. |
I am doing a full system upgrade to nightly/master/current/whatever, updating all packages, rebooting, and only then running the normal package installations and CI task, see OpenMPT/openmpt@587eab4 and https://github.com/OpenMPT/openmpt/blob/0eafb124cfd15f94e32302734607e71f2c36c84f/.github/workflows/Haiku-Autotools.yml#L39-L50. This works for me so far (well apart from Haiku always being generally one of the most flaky VMs for me). |
4 participants
Adds R1/beta6 to the supported Haiku versions.
Run the workflow for branches containing a slash
branches: '*'doesn't match a slash, so pushes to branches likefeature/foonever triggered the workflow.**matches across pathseparators. This commit (
dfbf9c3) is independent of the rest and can becherry-picked if you'd rather land it on its own.
Add support for Haiku R1/beta6
src/version.tspoints the Haiku image at haiku-builderv0.2.0, the firstrelease that ships an R1/beta6 image. That release also ships the R1/beta5
image, so the jobs pinned to R1/beta5 keep working
R1/beta6 hasn't been officially released yet, so the image is built from the
official test build,
hrev59866_53. That's noted in the readme and thechangelog, and the readme examples stay on R1/beta5, since that's the latest
released version.
Notes
v0.2.0reference only resolves once haiku-builder is tagged and released, so the
Haiku R1/beta6 CI job fails until then
npm run allpasses anddist/is regeneratedGenerated by Claude Code