/**
 * Single source of truth for the hippo-memory binary's package version.
 *
 * Bumped manually on every release alongside this file + four other package
 * manifests (package.json, openclaw.plugin.json,
 * extensions/openclaw-plugin/package.json,
 * extensions/openclaw-plugin/openclaw.plugin.json) and the lockfile —
 * five manifests in total carrying the version field.
 *
 * Used by:
 *   - src/db.ts rollback-safety guard (refuses to open a DB stamped with
 *     min_compatible_binary newer than this).
 *   - src/server.ts HTTP /health.
 *   - src/mcp/server.ts MCP serverInfo.
 *
 * Why not read package.json at runtime: the npm-published bundle ships
 * compiled `dist/` files that may not have package.json on a relative path
 * an ESM `import` can resolve cleanly, and a hardcoded constant survives
 * any packager that drops .json files.
 */
export declare const PACKAGE_VERSION = "1.15.0";
/**
 * Compare two semver strings. Returns positive if a > b, 0 if equal, negative
 * if a < b.
 *
 * v1.3.2 (claude review): pre-release/build-metadata tags throw rather than
 * silently coerce. The v1.3.1 implementation used `Number(n) || 0` which
 * parsed `'1-beta'` as 0, so `'1.3.1-beta'` → `[1,3,0]` and compared LESS
 * than `'1.3.1'`. If anyone ever stamped a pre-release version into
 * `meta.min_compatible_binary`, the rollback guard would silently misfire.
 * Loud failure is the right call on a security-relevant compare.
 *
 * Releases use plain `x.y.z` (no pre-release tags). If you need
 * pre-release semantics later, replace this with a real semver lib.
 */
export declare function compareSemver(a: string, b: string): number;
//# sourceMappingURL=version.d.ts.map