Skip to content

Bump Lemonade: 1bit-MONSTER/lemonade 2b491610b828 - #133

Merged
bong-water-water-bong merged 2 commits into
mainfrom
bump-lemonade/2b491610b828
Sep 26, 2026
Merged

bong-water-water-bong merged 2 commits into
mainfrom
bump-lemonade/2b491610b828

Conversation

@bong-water-water-bong

Copy link
Copy Markdown
Collaborator

Moves third_party/lemonade from fb65f488457f to the fork's main 2b491610b828.

Fork commits (last 30):

  • 6deeb05f7 Default release.py to unsigned tags (#3660)
  • 2b491610b Sync upstream lemonade-sdk/lemonade main (6deeb05f77b3)

CI here has no GPU. Before merging, on Strix Halo:
scripts/build-lemonade.sh ~/.cache/lemonade-pin, then Lemonade's LLM suite through the onebit recipe (docs/lemonade.md).

@context7

context7 Bot commented Sep 26, 2026 •

Copy link
Copy Markdown

Docs7 for 1bit-monster/engine

Result Status Action
Deployment ➖ Not used —
Content review ➖ Did not run. This site has no agent runs available this month. Wait for the monthly reset or check your Docs7 plan. —

Commit 63e3665

@github-actions

github-actions Bot commented Sep 26, 2026 •

Copy link
Copy Markdown

PR Reviewer Guide 🔍

(Review updated until commit 63e3665)

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ No major issues detected

bong-water-water-bong added a commit that referenced this pull request Sep 26, 2026
…; name the failing step (#135)

Found by a dry-run rehearsal: the suite expects a lemond already listening (port 13305) and
needs numpy from test/requirements.txt, so the Lemonade bump was held for the wrong reason, and
the held reason quoted the (passing) ctest log. Now lemond from the build runs on its own port
for the suite; a held bump names the step and the log that failed. First-release notes say
"commit" for a new pin and drop "None →".

Rehearsal on Strix Halo (WEEKLY_DRY_RUN=1): #132 (ZINC) and #133 (Lemonade) pass; Lemonade's
LLM suite through onebit on Vulkan: Ran 31 tests, OK (skipped=2).

Co-authored-by: bong-water-water-bong <bong-water-water-bong@1bit.gg>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

Persistent review updated to latest commit 63e3665

@bong-water-water-bong

Copy link
Copy Markdown
Collaborator Author

Verified on Strix Halo (Sunday-run rehearsal, scripts/weekly.sh bumps stage): this PR merged onto main, full build (Vulkan, HRX, lean, ZINC, ONNX, DwarfStar, NPU), ctest 11/11, then scripts/build-lemonade.sh and Lemonade's LLM suite through the onebit recipe on Vulkan against the built lemond: Ran 31 tests, OK (skipped=2: echo, generation parameters, as for llamacpp).

@bong-water-water-bong
bong-water-water-bong merged commit 77a43e3 into main Sep 26, 2026
3 checks passed
@bong-water-water-bong
bong-water-water-bong deleted the bump-lemonade/2b491610b828 branch September 26, 2026 13:29
bong-water-water-bong added a commit that referenced this pull request Sep 26, 2026
…n the model rows (#136)

- pins_on_branch, before the build: every pin a PR moves must be on the branch .gitmodules
  names for that submodule (GitHub compare: identical or ahead). Twice this week an engine PR
  pinned a fork commit on no branch (#103, #106); the shallow clones follow the branch and
  could not have fetched it.
- bump-hrx/* and bump-llama-vulkan/*: every hrx / vulkan row of registry/check_models.tsv
  through registry_check (serve end to end per architecture: ZAYA1, the Qwen MoE models,
  GLM, MiniCPM), under the memory guard; any FAIL holds the bump. Build + ctest alone serve
  one small GGUF, which would not notice an architecture breaking.

Tested pins_on_branch against the open PRs: #121's llama.cpp pin f59f6d37 fails (diverged from
1bit/hrx-vulkan-patched); the ZINC (#132) and Lemonade (#133) pins pass.

Co-authored-by: bong-water-water-bong <bong-water-water-bong@1bit.gg>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant