export interface UpdateCheck {
    /** Newest version advertised by any server we sync to. */
    serverVersion: string;
    /**
     * Newest version on the public npm registry, when it could be reached.
     *
     * The server was the ONLY source, and it cannot be: `cli.version` comes from
     * `/app/install/cli-version.txt`, a file stamped into the server's Docker
     * image and cached for the life of the process. So the advertised version is
     * whatever was current when that IMAGE was built, and it stays that way until
     * the image is rebuilt and rolled. A release published to npm is invisible
     * until then — 0.5.32 was live on the registry while every CLI on earth was
     * still being told "0.5.31 is available", which is the one thing this file
     * exists to get right.
     *
     * Optional: absent on a cache written by an older CLI, and absent whenever
     * the registry cannot be reached, which is the normal state of an air-gapped
     * install and must degrade to exactly the old behaviour.
     */
    npmVersion?: string;
    /** When we last asked (epoch ms). */
    checkedAt: number;
}
/** The newest version known from any source, and where it can be had. */
export declare function newestKnown(c: UpdateCheck): {
    version: string;
    source: 'server' | 'npm';
};
/**
 * The pending-update line, or null when current/unknown. Pure read of the
 * cached probe — no I/O beyond one small file, safe on every command.
 */
export declare function updateNotice(): string | null;
/** Ask each logged-in server what it serves, and cache the newest. Best-effort. */
export declare function refreshUpdateCheck(force?: boolean): Promise<UpdateCheck | null>;
export declare function printUpdateNotice(): void;
//# sourceMappingURL=update-notice.d.ts.map