Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix npm package missing qa/ assets causes completion cache failure [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#63815•Fetched 2026-04-10 03:41:49
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
scottgl9scottgl9
Participants
scottgl9scottgl9
Timeline (top)
cross-referenced ×1

The published npm package for [email protected] appears to exclude qa/ assets, but the packaged runtime still expects them.

This causes installed CLI builds to fail during completion cache update with:

Completion cache update failed ([openclaw] Failed to start CLI: Error: qa scenario pack not found: qa/scenarios/index.md)

Error Message

Running:

Root Cause

In the installed package:

  • runtime code in dist/suite-*.js reads qa/scenarios/index.md
  • but package.json's files allowlist does not include qa/

So the published package contains code that references files that were not shipped.

Fix Action

Fixed

PR fix notes

PR #63817: fix: include QA scenario pack in npm package

Description (problem / solution / changelog)

Summary

  • include qa/ in the published npm package files allowlist
  • ship the QA scenario pack assets that packaged runtime code already expects
  • fix completion cache update / QA scenario loading failures in installed npm builds

Problem

The published [email protected] npm package ships runtime code that expects QA scenario assets at qa/scenarios/index.md, but package.json excludes qa/ from the files allowlist.

That causes installed builds to fail with errors like:

Completion cache update failed ([openclaw] Failed to start CLI: Error: qa scenario pack not found: qa/scenarios/index.md)

Root cause

In the published package:

  • dist/suite-*.js reads qa/scenarios/index.md
  • package.json includes assets/, dist/, docs/, skills/, etc.
  • but it does not include qa/

So the packaged runtime references files that are never shipped.

Evidence

On an installed [email protected] package:

  • package root contains assets/, dist/, docs/, skills/, scripts/
  • package root does not contain qa/
  • packaged runtime still references qa/scenarios/index.md

Fix

Add qa/ to the npm package files allowlist in package.json.

Related

  • Fixes the completion-cache failure seen after openclaw update
  • Related issue: #63815

Changed files

  • package.json (modified, +1/-0)

Code Example

Completion cache update failed ([openclaw] Failed to start CLI: Error: qa scenario pack not found: qa/scenarios/index.md)

---

openclaw update

---

Completion cache update failed ([openclaw] Failed to start CLI: Error: qa scenario pack not found: qa/scenarios/index.md

---

"files": [
  "CHANGELOG.md",
  "LICENSE",
  "openclaw.mjs",
  "README.md",
  "assets/",
  "dist/",
  "docs/",
  "qa/",
  "skills/"
]
RAW_BUFFERClick to expand / collapse

Summary

The published npm package for [email protected] appears to exclude qa/ assets, but the packaged runtime still expects them.

This causes installed CLI builds to fail during completion cache update with:

Completion cache update failed ([openclaw] Failed to start CLI: Error: qa scenario pack not found: qa/scenarios/index.md)

Observed behavior

Running:

openclaw update

finishes the main update, then fails during plugin/completion cache update with:

Completion cache update failed ([openclaw] Failed to start CLI: Error: qa scenario pack not found: qa/scenarios/index.md

Root cause

In the installed package:

  • runtime code in dist/suite-*.js reads qa/scenarios/index.md
  • but package.json's files allowlist does not include qa/

So the published package contains code that references files that were not shipped.

Evidence

Installed package root contained:

  • assets/
  • dist/
  • docs/
  • skills/
  • scripts/

But no qa/ directory.

Installed package.json files allowlist includes:

  • assets/
  • dist/
  • docs/
  • skills/
  • selected scripts/...

and does not include:

  • qa/

Meanwhile the packaged runtime includes references to:

  • qa/scenarios/index.md

Suggested fix

Add qa/ to the npm package files allowlist in package.json.

Minimal fix

"files": [
  "CHANGELOG.md",
  "LICENSE",
  "openclaw.mjs",
  "README.md",
  "assets/",
  "dist/",
  "docs/",
  "qa/",
  "skills/"
]

Happy to open a PR for the one-line packaging fix if useful.

extent analysis

TL;DR

Add the missing qa/ directory to the files allowlist in package.json to ensure it is included in the published npm package.

Guidance

  • Verify that the qa/ directory is present in the project repository and contains the required files, such as qa/scenarios/index.md.
  • Update the files allowlist in package.json to include the qa/ directory, as shown in the suggested fix.
  • Test the updated package by running openclaw update to ensure the completion cache update completes successfully.
  • Consider opening a PR with the proposed fix to update the packaging configuration.

Example

The updated package.json files allowlist should include the qa/ directory, as shown:

"files": [
  "CHANGELOG.md",
  "LICENSE",
  "openclaw.mjs",
  "README.md",
  "assets/",
  "dist/",
  "docs/",
  "qa/",
  "skills/"
]

Notes

This fix assumes that the qa/ directory is intended to be included in the published package and that its contents are required by the runtime code.

Recommendation

Apply the suggested fix by updating the files allowlist in package.json to include the qa/ directory, as this will ensure that the required files are included in the published package and the completion cache update completes successfully.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#database connection#vector store#embedding generation#cache error#pipeline error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING