Interface PackageConfig

packages/bumpy/src/types.ts:197–227

}

export interface PackageConfig {
  /** Explicitly opt in or out of version management (overrides private/ignore/include) */
  managed?: boolean;
  /**
   * When `false`, this package can never be bumped directly by a bump file — it only
   * receives propagated bumps (fixed/linked groups, cascades, dependency updates).
   *
   * Use this for derived artifacts that version in lockstep with a driver package —
   * the typical case is platform-specific binary packages (`@mycli/bin-*`) published
   * alongside a core package and kept in a `fixed` group with it. Effects:
   * - `bumpy add` / `bumpy generate` never select or suggest the package
   * - a bump file that directly names it (with a type other than `none`) is an error
   * - `bumpy check` considers its changes covered when a bump file covers any other
   *   member of its fixed group, and points there when one is missing
   */
  directBump?: boolean;
  access?: 'public' | 'restricted';
  publishCommand?: string | string[];
  buildCommand?: string;
  registry?: string;
  skipNpmPublish?: boolean;
  /** Command to check if a version is already published. Should output the published version string. */
  checkPublished?: string;
  /** Glob patterns to filter which changed files count toward marking this package as changed */
  changedFilePatterns?: string[];
  dependencyBumpRules?: Partial<Record<DepType, DependencyBumpRule | false>>;
  cascadeTo?: CascadeConfig;
  cascadeFrom?: CascadeConfig;
  /**
   * Names (or globs) of `devDependencies` that should be treated as release-relevant:
   * a change to one requires a release of this package, and (for internal workspace
   * deps) its own releases cascade here. `devDependencies` are ignored for versioning by
   * default — this opts specific entries back in.
   *