Skip to content

chore[skiplog|notask]: backmerge release-openclaw-plugin-0.2.1 — version bump, manifest, cli dep floor, changelog - #3997

Draft
simon-iribarren wants to merge 2 commits into
mainfrom
backmerge/release-openclaw-plugin-0.2.1
Draft

chore[skiplog|notask]: backmerge release-openclaw-plugin-0.2.1 — version bump, manifest, cli dep floor, changelog#3997
simon-iribarren wants to merge 2 commits into
mainfrom
backmerge/release-openclaw-plugin-0.2.1

Conversation

@simon-iribarren

Copy link
Copy Markdown
Contributor

🎯 What problem does this PR solve?

  • Lands the release metadata for @qvac/openclaw-plugin@0.2.1 on main, per gitflow.md "Keep main aligned", so future development and the next changelog base see the shipped version.
  • Without it, main keeps the plugin at 0.2.0 with a @qvac/cli floor of ^0.11.0 that no longer matches the host its launcher starts.

📝 How does it solve it?

Cherry-picks (-x) the single release commit from release-openclaw-plugin-0.2.1. No functional changes; tagged [skiplog] so it does not appear in future changelogs.

  • plugins/openclaw/package.json — version 0.2.00.2.1, @qvac/cli ^0.11.0^0.12.0
  • plugins/openclaw/openclaw.plugin.json — manifest version 0.2.00.2.1
  • plugins/openclaw/changelog/0.2.1/CHANGELOG.md, CHANGELOG_LLM.md
  • plugins/openclaw/CHANGELOG.md — aggregate rebuilt

Companion release PR: #3996

🧪 How was it tested?

  • A straight cherry-pick is correct here rather than a hand-crafted backmerge: release-openclaw-plugin-0.2.1 was cut from the current main tip in this same session, so there is no dependency divergence between the release branch and main to regress. @qvac/ai-sdk-provider is untouched at ^0.6.0, and the @qvac/cli floor moves forward to match the CLI 0.12 cut, so no dependency goes backwards.
  • git diff --stat upstream/main..HEAD shows only the five release-metadata files above, with both version fields (package.json and openclaw.plugin.json) landing at 0.2.1.
  • Cherry-pick applied with no conflicts.

Dependency floor alignment for the @qvac/cli 0.12 line. No plugin
behaviour changes.

- version 0.2.0 -> 0.2.1 (package.json + openclaw.plugin.json)
- @qvac/cli dependency ^0.11.0 -> ^0.12.0
- changelog/0.2.1/ (CHANGELOG.md, CHANGELOG_LLM.md)
- aggregated CHANGELOG.md rebuilt

(cherry picked from commit 5978ba2)
@github-actions

github-actions Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

License compliance — clean

No new dependency license findings in this PR.

Warn-only (shadow) mode — this check does not block merges yet.

Updated automatically by the canonical license compliance workflow.

NOTICE presence (advisory)

Missing NOTICE (advisory, does not block):

  • ./.github/actions/release-merge-guard
  • ./docs/website
  • ./packages/ggml-coload-smoke
  • ./packages/fabric/test/integration
  • ./packages/inference-addon-cpp/mobile
  • ./packages/sdk/e2e
  • ./packages/llm-llamacpp/benchmarks/performance
  • ./packages/llm-llamacpp/benchmarks/server
  • ./packages/vla-ggml/sim/server
  • ./packages/embed-llamacpp/benchmarks/performance
  • ./packages/embed-llamacpp/benchmarks/server
  • ./packages/asr-ggml/benchmarks/server

opaninakuffo
opaninakuffo previously approved these changes Aug 24, 2026
Victor-Rodzko
Victor-Rodzko previously approved these changes Aug 24, 2026
The 0.2.1 notes claimed nothing changes for users. That was wrong:
createQvacServeModels writes every catalog model with
preload: entry.id === options.model, so the 7 non-selected models were
preload:false. On CLI 0.11 those never loaded and returned
503 model_not_ready forever, making model switching in OpenClaw fail.
CLI 0.12 lazy-loads them on first request.

- CHANGELOG.md: add the fix entry
- CHANGELOG_LLM.md: lead with the model-switching fix
- aggregated CHANGELOG.md rebuilt

(cherry picked from commit 69731e4)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants