/**
 * Fetch the `auden` package's npm dist-tags.
 *
 * Uses the dist-tags endpoint rather than the full packument: it returns a
 * small object (`{"latest":"0.2.0","alpha":"0.3.0-alpha.1"}`) instead of every
 * version's metadata, and one request covers every channel the CLI might be
 * running on.
 *
 * The registry URL is hardcoded to the public registry on purpose — the same
 * reasoning as `scripts/ci/release-alpha.ts`: a user's `.npmrc` or
 * `NPM_CONFIG_REGISTRY` could point at a private or lagging mirror, which
 * would produce a wrong (possibly backward) answer about what the current
 * release is.
 */
export type FetchDistTagsOptions = {
    fetchImpl?: typeof fetch;
    url?: string;
    timeoutMs?: number;
};
/**
 * Return the dist-tag → version map, or null on any failure.
 *
 * Every error path yields null rather than throwing: being offline, behind a
 * proxy, or rate-limited is an ordinary state for a developer machine, and an
 * update check is strictly advisory — it must never turn into a visible error
 * on an unrelated command.
 */
export declare function fetchDistTags(options?: FetchDistTagsOptions): Promise<Record<string, string> | null>;
/**
 * Timeout for a check somebody explicitly asked for (`auden update`).
 *
 * Longer than {@link DIST_TAGS_TIMEOUT_MS} because the trade-off inverts: the
 * passive notice rides an unrelated command and must never delay it, while a
 * forced check *is* the command and has nothing to be late for. At 2s a
 * proxied or cold registry request loses routinely, and each loss records a
 * failed attempt that backs the next check off for a further
 * `UPDATE_CACHE_TTL_MS`.
 */
export declare const FORCED_DIST_TAGS_TIMEOUT_MS = 10000;
//# sourceMappingURL=registry.d.ts.map