@exadev/semantic-release-workspace 1.3.2 → 1.3.3

package/dist/cli.js

@@ -15,7 +15,7 @@ import { generateNotes } from "@semantic-release/release-notes-generator";
 import semanticRelease from "semantic-release";
 import { pathToFileURL } from "node:url";
 //#region package.json
-var version = "1.3.2";
+var version = "1.3.3";
 //#endregion
 //#region src/errors.ts
 /**

package/dist/index.d.cts

@@ -1,7 +1,7 @@
 import { AnalyzeCommitsContext, BranchSpec, Commit, GenerateNotesContext } from "semantic-release";
 import { ReleaseGateState } from "@exadev/release-gate";
 //#region src/package-name.d.ts
-declare const packageName = "@exadev/semantic-release-workspace";
+export declare const packageName = "@exadev/semantic-release-workspace";
 //#endregion
 //#region src/manifest.d.ts
 /**
@@ -16,13 +16,13 @@ interface PackageManifest {
   /** Only the fields actually present in the file, each mapping dependency name to its declared range. */
   readonly dependencies: ReadonlyMap<DependencyField, ReadonlyMap<string, string>>;
 }
-declare function readManifest(path: string): Promise<PackageManifest>;
+export declare function readManifest(path: string): Promise<PackageManifest>;
 /**
  * Rewrites one dependency range in a manifest on disk.
  *
  * Deliberately re-reads the file rather than editing a copy held from discovery time: by the time a cross-package bump is applied, semantic-release's own `@semantic-release/npm` prepare step may already have rewritten `version` in this same file for an earlier package in the run. Writing back a manifest parsed before that would silently revert it.
  */
-declare function writeDependencyRange(path: string, field: DependencyField, dependency: string, range: string): Promise<void>;
+export declare function writeDependencyRange(path: string, field: DependencyField, dependency: string, range: string): Promise<void>;
 //#endregion
 //#region src/workspace.d.ts
 interface WorkspacePackage {
@@ -48,7 +48,7 @@ interface Workspace {
  *
  * Nothing here knows anything about a particular repository's layout: the globs come from the workspace file, and the package names, versions, and dependency ranges come from the manifests those globs match. Pointing this at any pnpm workspace is the entire configuration.
  */
-declare function discoverWorkspace(root: string): Promise<Workspace>;
+export declare function discoverWorkspace(root: string): Promise<Workspace>;
 //#endregion
 //#region src/graph.d.ts
 /** One package's dependency on another package in the same workspace. */
@@ -73,7 +73,7 @@ interface DependencyGraph {
  *
  * A dependency on a package outside the workspace is not an edge: it neither constrains the release order nor gets rewritten when something here releases. A package that names itself becomes a self-edge, which `topologicalOrder` then reports as the one-package cycle it is, rather than being quietly dropped.
  */
-declare function buildDependencyGraph(packages: readonly WorkspacePackage[]): DependencyGraph;
+export declare function buildDependencyGraph(packages: readonly WorkspacePackage[]): DependencyGraph;
 /**
  * Orders packages so every package appears after every workspace sibling it depends on, using Kahn's algorithm.
  *
@@ -81,7 +81,7 @@ declare function buildDependencyGraph(packages: readonly WorkspacePackage[]): De
  *
  * A cycle has no valid order at all, so it throws rather than picking one of the wrong answers. In a release context an arbitrary order is worse than a failure: it would publish a package whose sibling dependency range points at a version that does not exist yet.
  */
-declare function topologicalOrder(graph: DependencyGraph): readonly string[];
+export declare function topologicalOrder(graph: DependencyGraph): readonly string[];
 //#endregion
 //#region src/version-range.d.ts
 /**
@@ -120,11 +120,11 @@ type DependencyRangeShape = {
  *
  * This never needs the version a sibling is releasing: every case above depends only on the shape of `current` itself, which is what lets `releaseWorkspace` validate every workspace dependency edge up front, before any package has published anything, rather than discovering an unsupported range only when the first dependency it names happens to release.
  */
-declare function classifyDependencyRange(current: string): DependencyRangeShape;
+export declare function classifyDependencyRange(current: string): DependencyRangeShape;
 /**
  * Computes what a dependency range on a workspace sibling becomes once that sibling releases `version`, by classifying the range's shape and then, for a rewritable shape, substituting `version` in place of the version it currently names.
  */
-declare function updateDependencyRange(current: string, version: string): DependencyRangeUpdate;
+export declare function updateDependencyRange(current: string, version: string): DependencyRangeUpdate;
 //#endregion
 //#region src/plugins.d.ts
 /**
@@ -144,9 +144,9 @@ interface DependencyBumpSource {
 /** A publish-pipeline plugin entry as the orchestrator accepts it: a module name, optionally with a config object. */
 type PublishPluginSpec = string | readonly [string] | readonly [string, Record<string, unknown>];
 /** The standard publish pipeline this orchestrator coordinates when a workspace configures none of its own. Every entry reuses the corresponding official plugin -- the orchestrator scopes and sequences them per package, it does not reimplement npm publishing, GitHub release creation, or changelog writing. */
-declare const DEFAULT_PUBLISH_PLUGINS: readonly PublishPluginSpec[];
+export declare const DEFAULT_PUBLISH_PLUGINS: readonly PublishPluginSpec[];
 /** The standard publish pipeline for `commitStrategy: 'single'`: the same as `DEFAULT_PUBLISH_PLUGINS` minus @semantic-release/git, which that mode never runs -- see `resolvePublishPlugins`'s `forbidGitPlugin` option for why it is rejected outright rather than merely unused. Single-commit mode does its own committing (one combined commit for every released package), so a `prepare`-step git plugin here would create the very per-package commits that mode exists to avoid. */
-declare const SINGLE_COMMIT_DEFAULT_PUBLISH_PLUGINS: readonly PublishPluginSpec[];
+export declare const SINGLE_COMMIT_DEFAULT_PUBLISH_PLUGINS: readonly PublishPluginSpec[];
 interface ScopedPlugins {
   readonly analyzeCommits: (pluginConfig: Record<string, unknown>, context: AnalyzeCommitsContext & {
     cwd: string;
@@ -162,7 +162,7 @@ interface ScopedPlugins {
  *
  * The `analyzeCommits` wrapper carries one addition beyond filtering: when the standard analyzer finds no releasable commits but a workspace dependency range of the package's has changed, it returns 'patch' anyway. A dependent whose only change is a dependency bump still needs a release for that range to reach the registry. "Has changed" is read from two sources, merged: bumps recorded in memory earlier in the current run (`scope.bumps`), and bumps recorded in the package's own filtered commit history via the trailer `dependency-bump-commit.ts` writes and reads -- the latter is what lets a run that starts after a previous run already committed and pushed the bump (a crash recovery, or simply a later run) reach the same decision, rather than depending on state that existed only inside the process that made the commit.
  */
-declare function createScopedPlugins(scope: {
+export declare function createScopedPlugins(scope: {
   readonly pkg: WorkspacePackage;
   readonly analyzeCommitsConfig: Record<string, unknown>;
   readonly generateNotesConfig: Record<string, unknown>;
@@ -175,12 +175,12 @@ declare function createScopedPlugins(scope: {
  *
  * A commit missing from the changed-paths map is kept rather than dropped: it is inside the package's release range (semantic-release put it there), so a failure to parse its file list must not silently swallow a release. Absent evidence errs towards publishing, which is the visible direction for a release tool.
  */
-declare function filterCommitsToDirectory<T extends {
+export declare function filterCommitsToDirectory<T extends {
   readonly hash: string;
 }>(commits: readonly T[], changedPaths: ReadonlyMap<string, ReadonlySet<string>>, directory: string): readonly T[];
 /** A publish plugin entry with its module name resolved to an absolute path, so semantic-release loads the workspace's installed plugins regardless of the package directory it runs from. */
 type ResolvedPublishPlugin = [string, Record<string, unknown>];
-declare function resolvePublishPlugins(specs: readonly PublishPluginSpec[], workspaceRoot: string, options: {
+export declare function resolvePublishPlugins(specs: readonly PublishPluginSpec[], workspaceRoot: string, options: {
   readonly requireGitPlugin: boolean;
   readonly forbidGitPlugin?: boolean;
 }): readonly ResolvedPublishPlugin[];
@@ -207,7 +207,7 @@ interface ResumeWorkspaceReleaseOptions {
 /**
  * Finishes every package a `gatePublish: true` `releaseWorkspace` run tagged and pushed but did not publish. Resumes each `detached` entry in the array's own order -- not re-derived from the workspace's dependency graph, since a resume pass may run in a separate process or checkout, where re-deriving order should only ever matter for directory lookup, not sequencing.
  */
-declare function resumeWorkspaceRelease(options: ResumeWorkspaceReleaseOptions): Promise<WorkspaceReleaseOutcome>;
+export declare function resumeWorkspaceRelease(options: ResumeWorkspaceReleaseOptions): Promise<WorkspaceReleaseOutcome>;
 //#endregion
 //#region src/release.d.ts
 /**
@@ -270,7 +270,7 @@ interface WorkspaceReleaseOutcome {
  *
  * For each package, in topological order: run semantic-release's programmatic API with `cwd` scoped to the package directory, a `name@version` tag format to keep each package's tags distinct in the one shared tag namespace, and inline `analyzeCommits`/`generateNotes` plugins that filter the release range's commits down to the package's own directory before delegating to the standard plugins. When a package releases, every workspace package that depends on it and has not run yet gets its dependency range rewritten in its manifest and committed immediately -- before its own turn, so its commit analysis and its published manifest both see the new range.
  */
-declare function releaseWorkspace(options?: ReleaseWorkspaceOptions): Promise<WorkspaceReleaseOutcome>;
+export declare function releaseWorkspace(options?: ReleaseWorkspaceOptions): Promise<WorkspaceReleaseOutcome>;
 //#endregion
 //#region src/errors.d.ts
 /**
@@ -278,27 +278,27 @@ declare function releaseWorkspace(options?: ReleaseWorkspaceOptions): Promise<Wo
  *
  * All of them are thrown, never returned as a status: the orchestrator deliberately has no "skip this package and carry on" path. A workspace that can't be discovered, ordered, or bumped correctly would otherwise publish a partially-consistent set of packages, which is strictly worse than publishing nothing.
  */
-declare class WorkspaceReleaseError extends Error {
+export declare class WorkspaceReleaseError extends Error {
   constructor(message: string);
 }
 /** The workspace itself could not be read: no `pnpm-workspace.yaml`, no `packages` globs, an unreadable or malformed `package.json`, two packages claiming the same name, or a package sitting at the workspace root (which cannot be path-scoped -- see `discoverWorkspace`). */
-declare class WorkspaceDiscoveryError extends WorkspaceReleaseError {}
+export declare class WorkspaceDiscoveryError extends WorkspaceReleaseError {}
 /** The intra-workspace dependency graph contains a cycle, so no release order exists in which every package releases after its own dependencies. */
-declare class DependencyCycleError extends WorkspaceReleaseError {
+export declare class DependencyCycleError extends WorkspaceReleaseError {
   /** The packages forming the cycle, in dependency order, with the first package repeated at the end so the loop reads end to end. */
   readonly cycle: readonly string[];
   constructor(cycle: readonly string[]);
 }
 /** A dependency on a workspace sibling uses a range this tool cannot rewrite with confidence. Rewriting it wrongly, or leaving it silently stale, both produce a published manifest that disagrees with the repository, so the run stops instead. */
-declare class UnsupportedDependencyRangeError extends WorkspaceReleaseError {}
+export declare class UnsupportedDependencyRangeError extends WorkspaceReleaseError {}
 /** The semantic-release options handed to the orchestrator cannot be scoped to a single package -- typically a publish plugin list that would leave a release commit or a cross-package manifest bump uncommitted. */
-declare class ReleaseConfigurationError extends WorkspaceReleaseError {}
+export declare class ReleaseConfigurationError extends WorkspaceReleaseError {}
 /** A git command the orchestrator runs itself (history filtering, dependency-bump commits, pushes) failed. Carries the exit code so callers can distinguish "configuration is missing" (exit 1) from real repository failures. */
-declare class GitCommandError extends WorkspaceReleaseError {
+export declare class GitCommandError extends WorkspaceReleaseError {
   readonly exitCode: number | undefined;
   constructor(args: readonly string[], cwd: string, exitCode: number | undefined, detail: string);
 }
 /** The workspace's git state does not support the release operation -- for example a detached HEAD, which names no branch that dependency-bump commits could be pushed to. */
-declare class WorkspaceStateError extends WorkspaceReleaseError {}
+export declare class WorkspaceStateError extends WorkspaceReleaseError {}
 //#endregion
-export { type AppliedDependencyBump, type CommitStrategy, DEFAULT_PUBLISH_PLUGINS, type DependencyBump, type DependencyBumpSource, DependencyCycleError, type DependencyField, type DependencyGraph, type DependencyRangeShape, type DependencyRangeUpdate, type DetachedPackageRelease, GitCommandError, type PackageManifest, type PackageReleaseOutcome, type PublishPluginSpec, ReleaseConfigurationError, type ReleaseWorkspaceOptions, type ResolvedPublishPlugin, type ResumeWorkspaceReleaseOptions, SINGLE_COMMIT_DEFAULT_PUBLISH_PLUGINS, type ScopedPlugins, UnsupportedDependencyRangeError, type Workspace, type WorkspaceDependency, WorkspaceDiscoveryError, type WorkspacePackage, WorkspaceReleaseError, type WorkspaceReleaseOutcome, WorkspaceStateError, buildDependencyGraph, classifyDependencyRange, createScopedPlugins, discoverWorkspace, filterCommitsToDirectory, packageName, readManifest, releaseWorkspace, resolvePublishPlugins, resumeWorkspaceRelease, topologicalOrder, updateDependencyRange, writeDependencyRange };
+export type { AppliedDependencyBump, CommitStrategy, DependencyBump, DependencyBumpSource, DependencyField, DependencyGraph, DependencyRangeShape, DependencyRangeUpdate, DetachedPackageRelease, PackageManifest, PackageReleaseOutcome, PublishPluginSpec, ReleaseWorkspaceOptions, ResolvedPublishPlugin, ResumeWorkspaceReleaseOptions, ScopedPlugins, Workspace, WorkspaceDependency, WorkspacePackage, WorkspaceReleaseOutcome };

package/dist/index.d.ts

@@ -1,7 +1,7 @@
 import { AnalyzeCommitsContext, BranchSpec, Commit, GenerateNotesContext } from "semantic-release";
 import { ReleaseGateState } from "@exadev/release-gate";
 //#region src/package-name.d.ts
-declare const packageName = "@exadev/semantic-release-workspace";
+export declare const packageName = "@exadev/semantic-release-workspace";
 //#endregion
 //#region src/manifest.d.ts
 /**
@@ -16,13 +16,13 @@ interface PackageManifest {
   /** Only the fields actually present in the file, each mapping dependency name to its declared range. */
   readonly dependencies: ReadonlyMap<DependencyField, ReadonlyMap<string, string>>;
 }
-declare function readManifest(path: string): Promise<PackageManifest>;
+export declare function readManifest(path: string): Promise<PackageManifest>;
 /**
  * Rewrites one dependency range in a manifest on disk.
  *
  * Deliberately re-reads the file rather than editing a copy held from discovery time: by the time a cross-package bump is applied, semantic-release's own `@semantic-release/npm` prepare step may already have rewritten `version` in this same file for an earlier package in the run. Writing back a manifest parsed before that would silently revert it.
  */
-declare function writeDependencyRange(path: string, field: DependencyField, dependency: string, range: string): Promise<void>;
+export declare function writeDependencyRange(path: string, field: DependencyField, dependency: string, range: string): Promise<void>;
 //#endregion
 //#region src/workspace.d.ts
 interface WorkspacePackage {
@@ -48,7 +48,7 @@ interface Workspace {
  *
  * Nothing here knows anything about a particular repository's layout: the globs come from the workspace file, and the package names, versions, and dependency ranges come from the manifests those globs match. Pointing this at any pnpm workspace is the entire configuration.
  */
-declare function discoverWorkspace(root: string): Promise<Workspace>;
+export declare function discoverWorkspace(root: string): Promise<Workspace>;
 //#endregion
 //#region src/graph.d.ts
 /** One package's dependency on another package in the same workspace. */
@@ -73,7 +73,7 @@ interface DependencyGraph {
  *
  * A dependency on a package outside the workspace is not an edge: it neither constrains the release order nor gets rewritten when something here releases. A package that names itself becomes a self-edge, which `topologicalOrder` then reports as the one-package cycle it is, rather than being quietly dropped.
  */
-declare function buildDependencyGraph(packages: readonly WorkspacePackage[]): DependencyGraph;
+export declare function buildDependencyGraph(packages: readonly WorkspacePackage[]): DependencyGraph;
 /**
  * Orders packages so every package appears after every workspace sibling it depends on, using Kahn's algorithm.
  *
@@ -81,7 +81,7 @@ declare function buildDependencyGraph(packages: readonly WorkspacePackage[]): De
  *
  * A cycle has no valid order at all, so it throws rather than picking one of the wrong answers. In a release context an arbitrary order is worse than a failure: it would publish a package whose sibling dependency range points at a version that does not exist yet.
  */
-declare function topologicalOrder(graph: DependencyGraph): readonly string[];
+export declare function topologicalOrder(graph: DependencyGraph): readonly string[];
 //#endregion
 //#region src/version-range.d.ts
 /**
@@ -120,11 +120,11 @@ type DependencyRangeShape = {
  *
  * This never needs the version a sibling is releasing: every case above depends only on the shape of `current` itself, which is what lets `releaseWorkspace` validate every workspace dependency edge up front, before any package has published anything, rather than discovering an unsupported range only when the first dependency it names happens to release.
  */
-declare function classifyDependencyRange(current: string): DependencyRangeShape;
+export declare function classifyDependencyRange(current: string): DependencyRangeShape;
 /**
  * Computes what a dependency range on a workspace sibling becomes once that sibling releases `version`, by classifying the range's shape and then, for a rewritable shape, substituting `version` in place of the version it currently names.
  */
-declare function updateDependencyRange(current: string, version: string): DependencyRangeUpdate;
+export declare function updateDependencyRange(current: string, version: string): DependencyRangeUpdate;
 //#endregion
 //#region src/plugins.d.ts
 /**
@@ -144,9 +144,9 @@ interface DependencyBumpSource {
 /** A publish-pipeline plugin entry as the orchestrator accepts it: a module name, optionally with a config object. */
 type PublishPluginSpec = string | readonly [string] | readonly [string, Record<string, unknown>];
 /** The standard publish pipeline this orchestrator coordinates when a workspace configures none of its own. Every entry reuses the corresponding official plugin -- the orchestrator scopes and sequences them per package, it does not reimplement npm publishing, GitHub release creation, or changelog writing. */
-declare const DEFAULT_PUBLISH_PLUGINS: readonly PublishPluginSpec[];
+export declare const DEFAULT_PUBLISH_PLUGINS: readonly PublishPluginSpec[];
 /** The standard publish pipeline for `commitStrategy: 'single'`: the same as `DEFAULT_PUBLISH_PLUGINS` minus @semantic-release/git, which that mode never runs -- see `resolvePublishPlugins`'s `forbidGitPlugin` option for why it is rejected outright rather than merely unused. Single-commit mode does its own committing (one combined commit for every released package), so a `prepare`-step git plugin here would create the very per-package commits that mode exists to avoid. */
-declare const SINGLE_COMMIT_DEFAULT_PUBLISH_PLUGINS: readonly PublishPluginSpec[];
+export declare const SINGLE_COMMIT_DEFAULT_PUBLISH_PLUGINS: readonly PublishPluginSpec[];
 interface ScopedPlugins {
   readonly analyzeCommits: (pluginConfig: Record<string, unknown>, context: AnalyzeCommitsContext & {
     cwd: string;
@@ -162,7 +162,7 @@ interface ScopedPlugins {
  *
  * The `analyzeCommits` wrapper carries one addition beyond filtering: when the standard analyzer finds no releasable commits but a workspace dependency range of the package's has changed, it returns 'patch' anyway. A dependent whose only change is a dependency bump still needs a release for that range to reach the registry. "Has changed" is read from two sources, merged: bumps recorded in memory earlier in the current run (`scope.bumps`), and bumps recorded in the package's own filtered commit history via the trailer `dependency-bump-commit.ts` writes and reads -- the latter is what lets a run that starts after a previous run already committed and pushed the bump (a crash recovery, or simply a later run) reach the same decision, rather than depending on state that existed only inside the process that made the commit.
  */
-declare function createScopedPlugins(scope: {
+export declare function createScopedPlugins(scope: {
   readonly pkg: WorkspacePackage;
   readonly analyzeCommitsConfig: Record<string, unknown>;
   readonly generateNotesConfig: Record<string, unknown>;
@@ -175,12 +175,12 @@ declare function createScopedPlugins(scope: {
  *
  * A commit missing from the changed-paths map is kept rather than dropped: it is inside the package's release range (semantic-release put it there), so a failure to parse its file list must not silently swallow a release. Absent evidence errs towards publishing, which is the visible direction for a release tool.
  */
-declare function filterCommitsToDirectory<T extends {
+export declare function filterCommitsToDirectory<T extends {
   readonly hash: string;
 }>(commits: readonly T[], changedPaths: ReadonlyMap<string, ReadonlySet<string>>, directory: string): readonly T[];
 /** A publish plugin entry with its module name resolved to an absolute path, so semantic-release loads the workspace's installed plugins regardless of the package directory it runs from. */
 type ResolvedPublishPlugin = [string, Record<string, unknown>];
-declare function resolvePublishPlugins(specs: readonly PublishPluginSpec[], workspaceRoot: string, options: {
+export declare function resolvePublishPlugins(specs: readonly PublishPluginSpec[], workspaceRoot: string, options: {
   readonly requireGitPlugin: boolean;
   readonly forbidGitPlugin?: boolean;
 }): readonly ResolvedPublishPlugin[];
@@ -207,7 +207,7 @@ interface ResumeWorkspaceReleaseOptions {
 /**
  * Finishes every package a `gatePublish: true` `releaseWorkspace` run tagged and pushed but did not publish. Resumes each `detached` entry in the array's own order -- not re-derived from the workspace's dependency graph, since a resume pass may run in a separate process or checkout, where re-deriving order should only ever matter for directory lookup, not sequencing.
  */
-declare function resumeWorkspaceRelease(options: ResumeWorkspaceReleaseOptions): Promise<WorkspaceReleaseOutcome>;
+export declare function resumeWorkspaceRelease(options: ResumeWorkspaceReleaseOptions): Promise<WorkspaceReleaseOutcome>;
 //#endregion
 //#region src/release.d.ts
 /**
@@ -270,7 +270,7 @@ interface WorkspaceReleaseOutcome {
  *
  * For each package, in topological order: run semantic-release's programmatic API with `cwd` scoped to the package directory, a `name@version` tag format to keep each package's tags distinct in the one shared tag namespace, and inline `analyzeCommits`/`generateNotes` plugins that filter the release range's commits down to the package's own directory before delegating to the standard plugins. When a package releases, every workspace package that depends on it and has not run yet gets its dependency range rewritten in its manifest and committed immediately -- before its own turn, so its commit analysis and its published manifest both see the new range.
  */
-declare function releaseWorkspace(options?: ReleaseWorkspaceOptions): Promise<WorkspaceReleaseOutcome>;
+export declare function releaseWorkspace(options?: ReleaseWorkspaceOptions): Promise<WorkspaceReleaseOutcome>;
 //#endregion
 //#region src/errors.d.ts
 /**
@@ -278,27 +278,27 @@ declare function releaseWorkspace(options?: ReleaseWorkspaceOptions): Promise<Wo
  *
  * All of them are thrown, never returned as a status: the orchestrator deliberately has no "skip this package and carry on" path. A workspace that can't be discovered, ordered, or bumped correctly would otherwise publish a partially-consistent set of packages, which is strictly worse than publishing nothing.
  */
-declare class WorkspaceReleaseError extends Error {
+export declare class WorkspaceReleaseError extends Error {
   constructor(message: string);
 }
 /** The workspace itself could not be read: no `pnpm-workspace.yaml`, no `packages` globs, an unreadable or malformed `package.json`, two packages claiming the same name, or a package sitting at the workspace root (which cannot be path-scoped -- see `discoverWorkspace`). */
-declare class WorkspaceDiscoveryError extends WorkspaceReleaseError {}
+export declare class WorkspaceDiscoveryError extends WorkspaceReleaseError {}
 /** The intra-workspace dependency graph contains a cycle, so no release order exists in which every package releases after its own dependencies. */
-declare class DependencyCycleError extends WorkspaceReleaseError {
+export declare class DependencyCycleError extends WorkspaceReleaseError {
   /** The packages forming the cycle, in dependency order, with the first package repeated at the end so the loop reads end to end. */
   readonly cycle: readonly string[];
   constructor(cycle: readonly string[]);
 }
 /** A dependency on a workspace sibling uses a range this tool cannot rewrite with confidence. Rewriting it wrongly, or leaving it silently stale, both produce a published manifest that disagrees with the repository, so the run stops instead. */
-declare class UnsupportedDependencyRangeError extends WorkspaceReleaseError {}
+export declare class UnsupportedDependencyRangeError extends WorkspaceReleaseError {}
 /** The semantic-release options handed to the orchestrator cannot be scoped to a single package -- typically a publish plugin list that would leave a release commit or a cross-package manifest bump uncommitted. */
-declare class ReleaseConfigurationError extends WorkspaceReleaseError {}
+export declare class ReleaseConfigurationError extends WorkspaceReleaseError {}
 /** A git command the orchestrator runs itself (history filtering, dependency-bump commits, pushes) failed. Carries the exit code so callers can distinguish "configuration is missing" (exit 1) from real repository failures. */
-declare class GitCommandError extends WorkspaceReleaseError {
+export declare class GitCommandError extends WorkspaceReleaseError {
   readonly exitCode: number | undefined;
   constructor(args: readonly string[], cwd: string, exitCode: number | undefined, detail: string);
 }
 /** The workspace's git state does not support the release operation -- for example a detached HEAD, which names no branch that dependency-bump commits could be pushed to. */
-declare class WorkspaceStateError extends WorkspaceReleaseError {}
+export declare class WorkspaceStateError extends WorkspaceReleaseError {}
 //#endregion
-export { type AppliedDependencyBump, type CommitStrategy, DEFAULT_PUBLISH_PLUGINS, type DependencyBump, type DependencyBumpSource, DependencyCycleError, type DependencyField, type DependencyGraph, type DependencyRangeShape, type DependencyRangeUpdate, type DetachedPackageRelease, GitCommandError, type PackageManifest, type PackageReleaseOutcome, type PublishPluginSpec, ReleaseConfigurationError, type ReleaseWorkspaceOptions, type ResolvedPublishPlugin, type ResumeWorkspaceReleaseOptions, SINGLE_COMMIT_DEFAULT_PUBLISH_PLUGINS, type ScopedPlugins, UnsupportedDependencyRangeError, type Workspace, type WorkspaceDependency, WorkspaceDiscoveryError, type WorkspacePackage, WorkspaceReleaseError, type WorkspaceReleaseOutcome, WorkspaceStateError, buildDependencyGraph, classifyDependencyRange, createScopedPlugins, discoverWorkspace, filterCommitsToDirectory, packageName, readManifest, releaseWorkspace, resolvePublishPlugins, resumeWorkspaceRelease, topologicalOrder, updateDependencyRange, writeDependencyRange };
+export type { AppliedDependencyBump, CommitStrategy, DependencyBump, DependencyBumpSource, DependencyField, DependencyGraph, DependencyRangeShape, DependencyRangeUpdate, DetachedPackageRelease, PackageManifest, PackageReleaseOutcome, PublishPluginSpec, ReleaseWorkspaceOptions, ResolvedPublishPlugin, ResumeWorkspaceReleaseOptions, ScopedPlugins, Workspace, WorkspaceDependency, WorkspacePackage, WorkspaceReleaseOutcome };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@exadev/semantic-release-workspace",
-  "version": "1.3.2",
+  "version": "1.3.3",
   "description": "Independent per-package semantic-release orchestration for pnpm workspaces, without lockstep versioning.",
   "type": "module",
   "repository": {
@@ -107,7 +107,7 @@
     "publint": "^0.3.23",
     "semantic-release": "^25.0.9",
     "signale": "^1.4.0",
-    "tsdown": "^0.22.14",
+    "tsdown": "^0.23.0",
     "turbo": "^2.10.11",
     "typescript": "^6.0.3",
     "typescript-eslint": "^8.67.0",