Skip to content

chore(deps): bump Lemonade Server to v10.7.0#1571

Open
github-actions[bot] wants to merge 5 commits into
mainfrom
deps/lemonade-10.7.0
Open

chore(deps): bump Lemonade Server to v10.7.0#1571
github-actions[bot] wants to merge 5 commits into
mainfrom
deps/lemonade-10.7.0

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Bumps the pinned Lemonade Server from v10.2.0 to v10.7.0. GAIA's installer and CI derive the Lemonade download URLs from LEMONADE_VERSION in src/gaia/version.py, so users running gaia init and the bundled desktop installer pick up the new release.

Notable in v10.7.0 (from the Lemonade release notes):

  • LMX-Omni multimodal models now work with any OpenAI-compatible app, plus server-side Omni orchestration for /chat/completions.
  • New lemonade bench command for apples-to-apples LLM benchmarking across llama.cpp, FastFlowLM, vLLM, and Ryzen AI SW.
  • Broader GPU coverage: llama.cpp CUDA on Windows/Linux, stable-diffusion.cpp CUDA on Linux and Vulkan on Windows/Linux; Linux ARM64 CPU/Vulkan backends.
  • New native Prometheus metrics endpoint for real-time stats monitoring.
  • Several security hardening fixes (path-traversal in /web-app/ and NPU cache download, prompt-injection in markdown links) and per-download SHA verification.
  • New models added: Gemma 4 12B and LFM2.5-8B-A1B.

⚠️ Heads-up — breaking change in v10.7.0: the deprecated lemond configuration environment variables were removed (use lemonade config instead). GAIA's own LEMONADE_* vars (LEMONADE_BASE_URL, LEMONADE_HOST, LEMONADE_PORT, …) are client-side connection settings and appear unaffected by this version bump, but a reviewer should confirm GAIA doesn't pass any removed server-side lemond env vars when launching/managing the server. No GAIA code change is included here for this; flagging for manual verification.

Test plan

  • CI green (lint + unit tests)
  • gaia init downloads Lemonade v10.7.0 successfully
  • Review the Lemonade release notes for breaking changes (default port, min ctx, API) that may need follow-up in GAIA beyond this version bump

itomek
itomek previously approved these changes Jun 10, 2026
kovtcharov-amd and others added 2 commits June 10, 2026 13:55
Doc version consistency check (util/check_doc_versions.py) flagged 8
stale v10.2.0 references across cpp/README.md, docs/cpp/setup.mdx, and
docs/guides/npu.mdx after the version.py bump. Bump them to 10.7.0 to
match LEMONADE_VERSION and turn the validate + code-quality checks green.
@github-actions

Copy link
Copy Markdown
Contributor Author

🟡 docs/docs.json:498 — navbar label still shows Lemonade 10.2.0 while every other reference in this PR was bumped to 10.7.0.

        "label": "v0.20.1 · Lemonade 10.7.0",

One-liner fix; otherwise the docs site navbar will advertise the wrong version after this merges.

jjswhub pushed a commit to jjswhub/gaia that referenced this pull request Jun 11, 2026
…#1573)

The Lemonade auto-bump workflow (amd#1552) opened its first real PR (amd#1571,
v10.2.0 → v10.7.0) tagged only `dependencies` and with no reviewers, so
bump PRs don't surface to the platform owners and miss the team's
Lemonade triage label. This adds the `lemonade 🍋` label and requests
both `kovtcharov-amd` and `itomek-amd` on every bump PR the workflow
opens.

Verified end-to-end: applied the same label + reviewers to the live test
PR amd#1571 via `gh pr edit` (the bot author can request both — confirms
the runtime `gh pr create --reviewer` path works), and both are repo
collaborators.

## Test plan
- [x] `lemonade 🍋` is the exact label name (space + emoji) — `gh label
list`
- [x] `kovtcharov-amd` and `itomek-amd` are collaborators (review
requests won't fail)
- [x] YAML parses
- [ ] Next scheduled/forced run opens a bump PR carrying both labels +
both reviewers

Co-authored-by: Ovtcharov <kovtchar@amd.com>
@github-actions

Copy link
Copy Markdown
Contributor Author

🟡 src/gaia/installer/init_command.py:103 — NPU profile min_lemonade_version wasn't updated

docs/guides/npu.mdx now says Lemonade v10.7.0+ is required, but the npu profile (and all seven other profiles) in INIT_PROFILES still gate on "10.2.0". A user with v10.2.0–v10.6.x installed will hit the "meets minimum" path and skip the upgrade prompt, but then fail at runtime if 10.7 is genuinely required.

    "npu": {
        ...
-        "min_lemonade_version": "10.2.0",
+        "min_lemonade_version": "10.7.0",

If the other profiles also need 10.7.0 features they should be updated too; at minimum the npu profile should match the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cpp dependencies Dependency updates documentation Documentation changes lemonade 🍋

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants