import type { SitecoreApiClientOptions } from "./types.js";
import { GraphQLRequestOptions } from "./graphql.js";
export declare const publishItems: (environment: SitecoreApiClientOptions, itemIds: string[], target?: string, options?: GraphQLRequestOptions) => Promise<{
    id: string;
    processedCount: number;
    stateName: string;
}>;
export declare const checkPublishStatus: (environment: SitecoreApiClientOptions, publishId: string, options?: GraphQLRequestOptions) => Promise<{
    id: string;
    processedCount: number;
    stateName: string;
}>;
export declare const fetchPublishingTargets: (environment: SitecoreApiClientOptions, options?: GraphQLRequestOptions) => Promise<string[]>;
/** Outcome of {@link publishItemSubtree}. */
export interface PublishItemSubtreeResult {
    /** Source item path that was published. */
    path: string;
    /** Source database the items were read from. */
    database: string;
    /** Publish target, when one was given. */
    target?: string;
    /** Number of items resolved under `path` and submitted to the job. */
    itemCount: number;
    /** The publish job receipt. */
    job: {
        id: string;
        processedCount: number;
        stateName: string;
    };
}
/**
 * Publish an item and all of its descendants in one job.
 *
 * Resolves every item under `path` via the Management API, then submits
 * the whole set to the publish pipeline. Throws (`INPUT_INVALID`) when
 * `path` resolves to no items. Composes `fetchItemMetadata` +
 * `publishItems` so callers (CLI, MCP, embedding SDK) get the workflow
 * rather than wiring the two raw calls themselves.
 */
export declare const publishItemSubtree: (environment: SitecoreApiClientOptions, path: string, options?: {
    database?: string;
    target?: string;
}) => Promise<PublishItemSubtreeResult>;