headroomlabs-ai/headroom · error · Error

${pkg.name} dependency ${name} mismatch: expected ${spec}, g

Error message

${pkg.name} dependency ${name} mismatch: expected ${spec}, got ${actual}

What it means

Error "${pkg.name} dependency ${name} mismatch: expected ${spec}, got ${actual}" thrown in headroomlabs-ai/headroom.

Source

Thrown at scripts/verify_npm_release_assets.mjs:125

for (const expected of packages) {
  const tarballPath = path.join(assetsDir, expected.tarball);
  tarballPaths.set(expected.name, tarballPath);
  const pkg = extractPackageJson(tarballPath);

  if (pkg.name !== expected.name) {
    throw new Error(`${expected.tarball} package name mismatch: expected ${expected.name}, got ${pkg.name}`);
  }
  if (pkg.version !== version) {
    throw new Error(`${expected.tarball} version mismatch: expected ${version}, got ${pkg.version}`);
  }

  assertNoFileDependencies(pkg);

  for (const [name, spec] of Object.entries(expected.dependencies || {})) {
    const actual = pkg.dependencies?.[name];
    if (actual !== spec) {
      throw new Error(`${pkg.name} dependency ${name} mismatch: expected ${spec}, got ${actual}`);
    }
  }

  if (expected.name === "headroom-openclaw") {
    const distPkg = extractDistPackageJson(tarballPath);
    if (distPkg.name !== expected.name) {
      throw new Error(`${expected.tarball} dist package name mismatch: expected ${expected.name}, got ${distPkg.name}`);
    }
    if (distPkg.version !== version) {
      throw new Error(`${expected.tarball} dist package version mismatch: expected ${version}, got ${distPkg.version}`);
    }
    assertNoFileDependencies(distPkg);
    for (const [name, spec] of Object.entries(expected.dependencies || {})) {
      const actual = distPkg.dependencies?.[name];
      if (actual !== spec) {
        throw new Error(`${distPkg.name} dist dependency ${name} mismatch: expected ${spec}, got ${actual}`);
      }
    }

View on GitHub (pinned to 322425c43b)

Solutions

  1. Update the dependency ${name} spec in ${pkg.name}'s package.json to the expected value ${spec}
  2. Re-run the release build so the packed manifest reflects the corrected spec

When it happens

Trigger: Raised by the npm release verifier when a packed package's dependency version spec differs from the expected pinned value.

Common situations: See trigger scenarios.


AI-assisted analysis of headroomlabs-ai/headroom@322425c43b (2026-08-15). Data as JSON: /api/errors/6d0cb38db619f98c. Report an issue: GitHub.