github/spec-kit · error · ValueError
Extension version mismatch: expected '{update['available']}'
Error message
Extension version mismatch: expected '{update['available']}', got '{preflight_manifest.version}' What it means
Error "Extension version mismatch: expected '{update['available']}', got '{preflight_manifest.version}'" thrown in github/spec-kit.
Source
Thrown at src/specify_cli/extensions/_commands.py:2014
manifest_file = Path(manifest_tmpdir) / "extension.yml"
manifest_file.write_bytes(manifest_bytes)
preflight_manifest = ExtensionManifest(manifest_file)
manager.check_compatibility(
preflight_manifest, speckit_version
)
zip_extension_id = preflight_manifest.id
if zip_extension_id != extension_id:
raise ValueError(
f"Extension ID mismatch: expected '{extension_id}', got '{zip_extension_id}'"
)
expected_version = pkg_version.Version(update["available"])
archive_version = pkg_version.Version(
preflight_manifest.version
)
if archive_version != expected_version:
raise ValueError(
"Extension version mismatch: "
f"expected '{update['available']}', "
f"got '{preflight_manifest.version}'"
)
# Match the remaining deterministic install validation
# before crossing the destructive boundary. The helper
# excludes this extension's current registry entry while
# still detecting namespace, core, duplicate, and
# cross-extension command conflicts.
manager._validate_install_conflicts(preflight_manifest)
new_command_names = list(
manager._collect_manifest_command_names(
preflight_manifest
)
)
new_skill_names = list(View on GitHub (pinned to bf88c9f9a8)
Solutions
- Fix the catalog 'available' version or the archive manifest version so they match, then retry the update.
When it happens
Trigger: Thrown at src/specify_cli/extensions/_commands.py:2014 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of github/spec-kit@bf88c9f9a8 (2026-08-14).
Data as JSON: /api/errors/4b59cac779464145.
Report an issue: GitHub.