@exadev/semantic-release-workspace 3.2.16 → 3.2.18

package/dist/cli.js

@@ -13,10 +13,9 @@ import { analyzeCommits } from "@semantic-release/commit-analyzer";
 import { generateNotes } from "@semantic-release/release-notes-generator";
 import semanticRelease from "semantic-release";
 import { pathToFileURL } from "node:url";
-//#region package.json
-var version = "3.2.16";
-//#endregion
-//#region src/errors.ts
+// package.json
+var version = "3.2.18";
+// src/errors.ts
 /**
 * Every failure this package raises deliberately is one of these, so a caller (or the CLI) can tell an orchestration failure it should report cleanly apart from an unexpected crash it should let propagate with a stack trace.
 *
@@ -74,8 +73,7 @@ function validateTagFormat(tagFormat) {
 function formatTagForPackage(tagFormat, name) {
 	return tagFormat.replaceAll("${name}", name);
 }
-//#endregion
-//#region src/json.ts
+// src/json.ts
 function isJsonObject(value) {
 	return typeof value === "object" && value !== null && !Array.isArray(value);
 }
@@ -105,8 +103,7 @@ function stringifyJsonLike(value, originalText) {
 	const serialised = JSON.stringify(value, null, detectIndent(originalText));
 	return originalText.endsWith("\n") ? `${serialised}\n` : serialised;
 }
-//#endregion
-//#region src/manifest.ts
+// src/manifest.ts
 const DEPENDENCY_FIELDS = [
 	"dependencies",
 	"devDependencies",
@@ -156,8 +153,7 @@ async function writeDependencyRange(path, field, dependency, range) {
 	declared[dependency] = range;
 	await writeFile(path, stringifyJsonLike(parsed, text), "utf8");
 }
-//#endregion
-//#region src/version-range.ts
+// src/version-range.ts
 const WORKSPACE_PROTOCOL = "workspace:";
 const CATALOG_PROTOCOL = "catalog:";
 const NPM_ALIAS_PROTOCOL = "npm:";
@@ -234,8 +230,7 @@ function updateDependencyRange(current, version) {
 		range: shape.workspacePrefixed ? `${WORKSPACE_PROTOCOL}${rewritten}` : rewritten
 	};
 }
-//#endregion
-//#region src/publishable-dependencies.ts
+// src/publishable-dependencies.ts
 /**
 * Throws `UnsupportedDependencyRangeError` unless every publishable package's installed dependencies (`dependencies`, `peerDependencies`, `optionalDependencies`) are ranges a consumer's package manager can resolve.
 *
@@ -255,8 +250,7 @@ function assertPublishableDependencies(packages) {
 	}
 	if (offences.length > 0) throw new UnsupportedDependencyRangeError(`Refusing to release: npm publish ships these dependency specifiers unchanged, so the published package could not be installed.\n${offences.join("\n")}\nDeclare a plain version range instead (for example "^1.2.3"). For a sibling in this workspace, keep "linkWorkspacePackages: true" in pnpm-workspace.yaml so pnpm still links it locally; this tool rewrites the range whenever the sibling releases. Packages marked "private" are never published and are exempt.`);
 }
-//#endregion
-//#region src/exec-file.ts
+// src/exec-file.ts
 /**
 * A hand-written promise wrapper around `child_process.execFile`, in place of `util.promisify(execFile)`: `execFile` synchronously returns a `ChildProcess` in addition to invoking its callback, which trips `@typescript-eslint/strict-void-return` when the whole function is handed to `promisify` (a value-returning function used where a void-returning one is contextually expected there) -- exactly the void-return contravariance leniency that rule exists to catch, even though `tsc` itself accepts the pattern. Calling `execFile` directly with our own callback, whose own return type really is `void`, sidesteps the mismatch instead of suppressing it.
 */
@@ -278,8 +272,7 @@ async function execFile$1(command, args, options) {
 		});
 	});
 }
-//#endregion
-//#region src/git.ts
+// src/git.ts
 /** Separates one commit's record in `git log --format` output. Chosen from the C0 control range so it can never appear in a hash or a file path. */
 const COMMIT_RECORD_SEPARATOR = "";
 /** The identity semantic-release's own core writes release commits under in CI when nothing else is configured (its COMMIT_NAME/COMMIT_EMAIL constants); dependency-bump commits use the same fallback so every commit a release run produces has a consistent author when the repository declares none. */
@@ -520,8 +513,7 @@ function toGitCommandError(args, cwd, cause) {
 	const stderr = cause instanceof Error && "stderr" in cause && typeof cause.stderr === "string" ? cause.stderr.trim() : "";
 	return new GitCommandError(args, cwd, exitCode, stderr !== "" ? stderr : cause instanceof Error ? cause.message : String(cause));
 }
-//#endregion
-//#region src/workspace.ts
+// src/workspace.ts
 /** The one filename pnpm recognises as a workspace definition. */
 const WORKSPACE_MANIFEST = "pnpm-workspace.yaml";
 /** Never treat an installed dependency's own manifest as a workspace package, however permissive the configured globs are. pnpm applies the same exclusion. */
@@ -601,8 +593,7 @@ function trimTrailingSlashes(pattern) {
 function toPosix(path) {
 	return sep === "/" ? path : path.split(sep).join("/");
 }
-//#endregion
-//#region src/graph.ts
+// src/graph.ts
 /**
 * Builds the inter-package dependency graph from the manifests alone.
 *
@@ -700,8 +691,7 @@ function mustGet(map, key, what) {
 	if (value === void 0) throw new WorkspaceReleaseError(`Internal error: ${what} "${key}" disappeared from the dependency graph mid-run.`);
 	return value;
 }
-//#endregion
-//#region src/bundling.ts
+// src/bundling.ts
 /**
 * Validates `bundlingPackages` against the workspace and works out, for every package, which workspace dependencies it bundles.
 *
@@ -732,11 +722,9 @@ function resolveBundledDependencies(graph, bundlingPackages) {
 function isPrivateRuntimeEdge(edge, graph) {
 	return edge.field !== "devDependencies" && mustGet(graph.packages, edge.dependency, "package").private;
 }
-//#endregion
-//#region src/package-name.ts
+// src/package-name.ts
 const packageName = "@exadev/semantic-release-workspace";
-//#endregion
-//#region src/release-type.ts
+// src/release-type.ts
 /** Every release type semantic-release knows, highest first: the order `@semantic-release/commit-analyzer` itself ranks them in (its `lib/default-release-types.js`), so comparing two types here agrees with how the analyzer picks the highest type among a package's own commits. */
 const RELEASE_TYPES_HIGHEST_FIRST = [
 	"major",
@@ -762,8 +750,7 @@ function highestReleaseType(types) {
 function raiseReleaseType(base, other) {
 	return other === void 0 || RELEASE_TYPES_HIGHEST_FIRST.indexOf(base) <= RELEASE_TYPES_HIGHEST_FIRST.indexOf(other) ? base : other;
 }
-//#endregion
-//#region src/dependency-bump-commit.ts
+// src/dependency-bump-commit.ts
 /**
 * The commit message format for a cross-package dependency-range bump, shared between the code that writes it (`bumpDependents` in `release.ts`) and the code that reads it back (`createScopedPlugins` in `plugins.ts`).
 *
@@ -803,8 +790,7 @@ function matchTrailerLine(message, key) {
 	const line = message.split("\n").find((candidate) => candidate.startsWith(prefix));
 	return line === void 0 ? void 0 : line.slice(prefix.length).trim();
 }
-//#endregion
-//#region src/plugins.ts
+// src/plugins.ts
 /** The one plugin a private package is kept off by default: see `resolveWorkspacePublishPlugins` for why a package that never reaches a registry does not get a public GitHub Release either. */
 const GITHUB_RELEASE_PLUGIN = "@semantic-release/github";
 /** semantic-release's own `getLastRelease` returns `{}` for a package with no prior tag -- not `undefined`, and not a fully-populated `LastRelease` -- contradicting the `gitHead: string` its own type declares. Narrows structurally rather than trusting that declared type, so a first-release context's `lastRelease` (correctly, at runtime) never claims a `gitHead` it does not have. */
@@ -1017,8 +1003,7 @@ async function releasePackageAcrossBranchMoves(name, branch, attempt, log) {
 		log(`${name}: reported no release while the branch moved from ${tipBefore} to ${tipAfter}, which is also what a stale branch looks like; integrating and releasing it again.`);
 	}
 }
-//#endregion
-//#region src/pnpm.ts
+// src/pnpm.ts
 /**
 * Regenerates `pnpm-lock.yaml` for the whole workspace from the manifests currently on disk, without touching `node_modules` or installing anything -- the same lockfile-refresh step a contributor runs by hand after editing a `package.json` dependency range.
 *
@@ -1033,8 +1018,7 @@ async function regenerateLockfile(options) {
 		throw new PnpmCommandError(options.cwd, detail);
 	}
 }
-//#endregion
-//#region src/single-commit-release.ts
+// src/single-commit-release.ts
 /**
 * `commitStrategy: 'single'`: one combined commit for the whole run instead of one commit per package release plus one per dependency bump.
 *
@@ -1380,8 +1364,7 @@ async function loadReleasePlugin(absolutePath, cache) {
 	cache.set(absolutePath, loaded);
 	return loaded;
 }
-//#endregion
-//#region src/release.ts
+// src/release.ts
 /**
 * Releases every package in a pnpm workspace with independent versions, in dependency order.
 *
@@ -1590,8 +1573,7 @@ function branchTracker(workspace, log) {
 		tip: async () => await fetchBranchTip(await currentBranch({ cwd: workspace.root }), { cwd: workspace.root })
 	};
 }
-//#endregion
-//#region src/gate-publish.ts
+// src/gate-publish.ts
 /**
 * The `gatePublish: true` half of `releaseWorkspace`: tags and pushes every due package via `@exadev/release-gate`'s `detachRelease`, but never publishes. Built on the same `runReleaseLoop` the normal per-package path uses, so dependency-range bumps between packages happen identically either way -- only the release call itself (`detachRelease` instead of `semanticRelease`) and how "did it release" gets read differ.
 */
@@ -1745,8 +1727,7 @@ async function resumeWorkspaceRelease(options) {
 		packages
 	};
 }
-//#endregion
-//#region src/cli.ts
+// src/cli.ts
 const CONFIG_OPTION_KEYS = /* @__PURE__ */ new Set([
 	"dryRun",
 	"branches",
@@ -1948,5 +1929,4 @@ createProgram().parseAsync(process.argv).catch((cause) => {
 	else console.error(String(cause));
 	process.exitCode = 1;
 });
-//#endregion
 export { createProgram, readReleaseConfigFile };

package/dist/index.cjs

@@ -1,5 +1,5 @@
 Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
-//#region \0rolldown/runtime.js
+// \0rolldown/runtime.js
 var __create = Object.create;
 var __defProp = Object.defineProperty;
 var __getOwnPropDesc = Object.getOwnPropertyDescriptor;
@@ -20,7 +20,6 @@ var __toESM = (mod, isNodeMode, target) => (target = mod != null ? __create(__ge
 	value: mod,
 	enumerable: true
 }) : target, mod));
-//#endregion
 let node_fs_promises = require("node:fs/promises");
 let node_path = require("node:path");
 let tinyglobby = require("tinyglobby");
@@ -35,10 +34,9 @@ let semantic_release = require("semantic-release");
 semantic_release = __toESM(semantic_release, 1);
 let node_url = require("node:url");
 let _exadev_release_gate = require("@exadev/release-gate");
-//#region src/package-name.ts
+// src/package-name.ts
 const packageName = "@exadev/semantic-release-workspace";
-//#endregion
-//#region src/errors.ts
+// src/errors.ts
 /**
 * Every failure this package raises deliberately is one of these, so a caller (or the CLI) can tell an orchestration failure it should report cleanly apart from an unexpected crash it should let propagate with a stack trace.
 *
@@ -81,8 +79,7 @@ var PnpmCommandError = class extends WorkspaceReleaseError {
 		super(`pnpm install --lockfile-only failed in ${cwd}: ${detail}`);
 	}
 };
-//#endregion
-//#region src/exec-file.ts
+// src/exec-file.ts
 /**
 * A hand-written promise wrapper around `child_process.execFile`, in place of `util.promisify(execFile)`: `execFile` synchronously returns a `ChildProcess` in addition to invoking its callback, which trips `@typescript-eslint/strict-void-return` when the whole function is handed to `promisify` (a value-returning function used where a void-returning one is contextually expected there) -- exactly the void-return contravariance leniency that rule exists to catch, even though `tsc` itself accepts the pattern. Calling `execFile` directly with our own callback, whose own return type really is `void`, sidesteps the mismatch instead of suppressing it.
 */
@@ -104,8 +101,7 @@ async function execFile(command, args, options) {
 		});
 	});
 }
-//#endregion
-//#region src/git.ts
+// src/git.ts
 /** Separates one commit's record in `git log --format` output. Chosen from the C0 control range so it can never appear in a hash or a file path. */
 const COMMIT_RECORD_SEPARATOR = "";
 /** The identity semantic-release's own core writes release commits under in CI when nothing else is configured (its COMMIT_NAME/COMMIT_EMAIL constants); dependency-bump commits use the same fallback so every commit a release run produces has a consistent author when the repository declares none. */
@@ -346,8 +342,7 @@ function toGitCommandError(args, cwd, cause) {
 	const stderr = cause instanceof Error && "stderr" in cause && typeof cause.stderr === "string" ? cause.stderr.trim() : "";
 	return new GitCommandError(args, cwd, exitCode, stderr !== "" ? stderr : cause instanceof Error ? cause.message : String(cause));
 }
-//#endregion
-//#region src/json.ts
+// src/json.ts
 function isJsonObject(value) {
 	return typeof value === "object" && value !== null && !Array.isArray(value);
 }
@@ -371,8 +366,7 @@ function stringifyJsonLike(value, originalText) {
 	const serialised = JSON.stringify(value, null, detectIndent(originalText));
 	return originalText.endsWith("\n") ? `${serialised}\n` : serialised;
 }
-//#endregion
-//#region src/manifest.ts
+// src/manifest.ts
 const DEPENDENCY_FIELDS = [
 	"dependencies",
 	"devDependencies",
@@ -422,8 +416,7 @@ async function writeDependencyRange(path, field, dependency, range) {
 	declared[dependency] = range;
 	await (0, node_fs_promises.writeFile)(path, stringifyJsonLike(parsed, text), "utf8");
 }
-//#endregion
-//#region src/workspace.ts
+// src/workspace.ts
 /** The one filename pnpm recognises as a workspace definition. */
 const WORKSPACE_MANIFEST = "pnpm-workspace.yaml";
 /** Never treat an installed dependency's own manifest as a workspace package, however permissive the configured globs are. pnpm applies the same exclusion. */
@@ -503,8 +496,7 @@ function trimTrailingSlashes(pattern) {
 function toPosix(path) {
 	return node_path.sep === "/" ? path : path.split(node_path.sep).join("/");
 }
-//#endregion
-//#region src/version-range.ts
+// src/version-range.ts
 const WORKSPACE_PROTOCOL = "workspace:";
 const CATALOG_PROTOCOL = "catalog:";
 const NPM_ALIAS_PROTOCOL = "npm:";
@@ -581,8 +573,7 @@ function updateDependencyRange(current, version) {
 		range: shape.workspacePrefixed ? `${WORKSPACE_PROTOCOL}${rewritten}` : rewritten
 	};
 }
-//#endregion
-//#region src/publishable-dependencies.ts
+// src/publishable-dependencies.ts
 /**
 * Throws `UnsupportedDependencyRangeError` unless every publishable package's installed dependencies (`dependencies`, `peerDependencies`, `optionalDependencies`) are ranges a consumer's package manager can resolve.
 *
@@ -602,8 +593,7 @@ function assertPublishableDependencies(packages) {
 	}
 	if (offences.length > 0) throw new UnsupportedDependencyRangeError(`Refusing to release: npm publish ships these dependency specifiers unchanged, so the published package could not be installed.\n${offences.join("\n")}\nDeclare a plain version range instead (for example "^1.2.3"). For a sibling in this workspace, keep "linkWorkspacePackages: true" in pnpm-workspace.yaml so pnpm still links it locally; this tool rewrites the range whenever the sibling releases. Packages marked "private" are never published and are exempt.`);
 }
-//#endregion
-//#region src/graph.ts
+// src/graph.ts
 /**
 * Builds the inter-package dependency graph from the manifests alone.
 *
@@ -701,8 +691,7 @@ function mustGet(map, key, what) {
 	if (value === void 0) throw new WorkspaceReleaseError(`Internal error: ${what} "${key}" disappeared from the dependency graph mid-run.`);
 	return value;
 }
-//#endregion
-//#region src/bundling.ts
+// src/bundling.ts
 /**
 * Validates `bundlingPackages` against the workspace and works out, for every package, which workspace dependencies it bundles.
 *
@@ -733,8 +722,7 @@ function resolveBundledDependencies(graph, bundlingPackages) {
 function isPrivateRuntimeEdge(edge, graph) {
 	return edge.field !== "devDependencies" && mustGet(graph.packages, edge.dependency, "package").private;
 }
-//#endregion
-//#region src/release-type.ts
+// src/release-type.ts
 /** Every release type semantic-release knows, highest first: the order `@semantic-release/commit-analyzer` itself ranks them in (its `lib/default-release-types.js`), so comparing two types here agrees with how the analyzer picks the highest type among a package's own commits. */
 const RELEASE_TYPES_HIGHEST_FIRST = [
 	"major",
@@ -760,8 +748,7 @@ function highestReleaseType(types) {
 function raiseReleaseType(base, other) {
 	return other === void 0 || RELEASE_TYPES_HIGHEST_FIRST.indexOf(base) <= RELEASE_TYPES_HIGHEST_FIRST.indexOf(other) ? base : other;
 }
-//#endregion
-//#region src/dependency-bump-commit.ts
+// src/dependency-bump-commit.ts
 /**
 * The commit message format for a cross-package dependency-range bump, shared between the code that writes it (`bumpDependents` in `release.ts`) and the code that reads it back (`createScopedPlugins` in `plugins.ts`).
 *
@@ -801,8 +788,7 @@ function matchTrailerLine(message, key) {
 	const line = message.split("\n").find((candidate) => candidate.startsWith(prefix));
 	return line === void 0 ? void 0 : line.slice(prefix.length).trim();
 }
-//#endregion
-//#region src/plugins.ts
+// src/plugins.ts
 /** The one plugin a private package is kept off by default: see `resolveWorkspacePublishPlugins` for why a package that never reaches a registry does not get a public GitHub Release either. */
 const GITHUB_RELEASE_PLUGIN = "@semantic-release/github";
 /** semantic-release's own `getLastRelease` returns `{}` for a package with no prior tag -- not `undefined`, and not a fully-populated `LastRelease` -- contradicting the `gitHead: string` its own type declares. Narrows structurally rather than trusting that declared type, so a first-release context's `lastRelease` (correctly, at runtime) never claims a `gitHead` it does not have. */
@@ -1015,8 +1001,7 @@ async function releasePackageAcrossBranchMoves(name, branch, attempt, log) {
 		log(`${name}: reported no release while the branch moved from ${tipBefore} to ${tipAfter}, which is also what a stale branch looks like; integrating and releasing it again.`);
 	}
 }
-//#endregion
-//#region src/pnpm.ts
+// src/pnpm.ts
 /**
 * Regenerates `pnpm-lock.yaml` for the whole workspace from the manifests currently on disk, without touching `node_modules` or installing anything -- the same lockfile-refresh step a contributor runs by hand after editing a `package.json` dependency range.
 *
@@ -1046,8 +1031,7 @@ function validateTagFormat(tagFormat) {
 function formatTagForPackage(tagFormat, name) {
 	return tagFormat.replaceAll("${name}", name);
 }
-//#endregion
-//#region src/single-commit-release.ts
+// src/single-commit-release.ts
 /**
 * `commitStrategy: 'single'`: one combined commit for the whole run instead of one commit per package release plus one per dependency bump.
 *
@@ -1393,8 +1377,7 @@ async function loadReleasePlugin(absolutePath, cache) {
 	cache.set(absolutePath, loaded);
 	return loaded;
 }
-//#endregion
-//#region src/gate-publish.ts
+// src/gate-publish.ts
 /**
 * The `gatePublish: true` half of `releaseWorkspace`: tags and pushes every due package via `@exadev/release-gate`'s `detachRelease`, but never publishes. Built on the same `runReleaseLoop` the normal per-package path uses, so dependency-range bumps between packages happen identically either way -- only the release call itself (`detachRelease` instead of `semanticRelease`) and how "did it release" gets read differ.
 */
@@ -1536,8 +1519,7 @@ async function resumeWorkspaceRelease(options) {
 		packages
 	};
 }
-//#endregion
-//#region src/release.ts
+// src/release.ts
 /**
 * Releases every package in a pnpm workspace with independent versions, in dependency order.
 *
@@ -1746,7 +1728,6 @@ function branchTracker(workspace, log) {
 		tip: async () => await fetchBranchTip(await currentBranch({ cwd: workspace.root }), { cwd: workspace.root })
 	};
 }
-//#endregion
 exports.DEFAULT_PUBLISH_PLUGINS = DEFAULT_PUBLISH_PLUGINS;
 exports.DependencyCycleError = DependencyCycleError;
 exports.GitCommandError = GitCommandError;

package/dist/index.d.cts

@@ -1,9 +1,6 @@
 import { AnalyzeCommitsContext, BranchSpec, Commit, GenerateNotesContext, ReleaseType } from "semantic-release";
 import { ReleaseGateState } from "@exadev/release-gate";
-//#region src/package-name.d.ts
 export declare const packageName = "@exadev/semantic-release-workspace";
-//#endregion
-//#region src/manifest.d.ts
 /**
  * The manifest fields that can name a workspace sibling.
  *
@@ -25,8 +22,6 @@ export declare function readManifest(path: string): Promise<PackageManifest>;
  * 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.
  */
 export declare function writeDependencyRange(path: string, field: DependencyField, dependency: string, range: string): Promise<void>;
-//#endregion
-//#region src/workspace.d.ts
 interface WorkspacePackage {
   readonly name: string;
   readonly version: string;
@@ -53,8 +48,6 @@ 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.
  */
 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. */
 interface WorkspaceDependency {
   /** The depending package's name. */
@@ -88,8 +81,6 @@ export declare function buildDependencyGraph(packages: readonly WorkspacePackage
 export declare function topologicalOrder(graph: DependencyGraph): readonly string[];
 /** The packages a release order names, in that order, for the stages that need each package's manifest rather than only its name. */
 export declare function orderedPackages(graph: DependencyGraph, order: readonly string[]): readonly WorkspacePackage[];
-//#endregion
-//#region src/version-range.d.ts
 /**
  * What happens to one dependency range when the sibling it points at releases a new version.
  *
@@ -131,8 +122,6 @@ export declare function classifyDependencyRange(current: string): DependencyRang
  * 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.
  */
 export declare function updateDependencyRange(current: string, version: string): DependencyRangeUpdate;
-//#endregion
-//#region src/bundling.d.ts
 /**
  * Which of a package's workspace dependencies ship inside its published artefact, as far as release types are concerned. Built by `resolveBundledDependencies`.
  */
@@ -156,8 +145,6 @@ interface BundledDependencies {
  * `bundlingPackages` names public workspace packages whose builds bundle their workspace `devDependencies`; `undefined` or an empty list leaves every package's release type as it was. Returns one entry per package in the graph. Throws `ReleaseConfigurationError` when a name is not a package in the workspace, or names a private package, which never publishes and so ships nothing to consumers.
  */
 export declare function resolveBundledDependencies(graph: DependencyGraph, bundlingPackages: readonly string[] | undefined): ReadonlyMap<string, BundledDependencies>;
-//#endregion
-//#region src/plugins.d.ts
 /**
  * One workspace dependency range that changed because its package released a new version during this run. `rewritten` means the dependent's manifest was edited on disk; `resolved-at-publish` means a bare `workspace:^`-style range whose on-disk text is unchanged. Both count towards the dependent's release.
  */
@@ -248,8 +235,6 @@ export declare function resolveWorkspacePublishPlugins(packages: readonly Publis
   readonly requireGitPlugin: boolean;
   readonly forbidGitPlugin?: boolean;
 }): ReadonlyMap<string, readonly ResolvedPublishPlugin[]>;
-//#endregion
-//#region src/gate-publish.d.ts
 /**
  * One package's outcome from a gated (`gatePublish: true`) detach pass -- what `resumeWorkspaceRelease` needs later to finish publishing it. `relativeDirectory`, not the absolute `directory`, is what a resume pass actually uses to resolve `cwd`: a resume can run against a different checkout of the same repository (a separate CI job, a separate clone) at a different absolute path, and `relativeDirectory` is the portable part.
  */
@@ -272,8 +257,6 @@ 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.
  */
 export declare function resumeWorkspaceRelease(options: ResumeWorkspaceReleaseOptions): Promise<WorkspaceReleaseOutcome>;
-//#endregion
-//#region src/release.d.ts
 /**
  * How a run commits its released changes:
  *
@@ -366,8 +349,6 @@ 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.
  */
 export declare function releaseWorkspace(options?: ReleaseWorkspaceOptions): Promise<WorkspaceReleaseOutcome>;
-//#endregion
-//#region src/errors.d.ts
 /**
  * Every failure this package raises deliberately is one of these, so a caller (or the CLI) can tell an orchestration failure it should report cleanly apart from an unexpected crash it should let propagate with a stack trace.
  *
@@ -395,5 +376,4 @@ export declare class GitCommandError extends WorkspaceReleaseError {
 }
 /** 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. */
 export declare class WorkspaceStateError extends WorkspaceReleaseError {}
-//#endregion
 export type { AppliedDependencyBump, BundledDependencies, CommitStrategy, DependencyBump, DependencyBumpSource, DependencyField, DependencyGraph, DependencyRangeShape, DependencyRangeUpdate, DetachedPackageRelease, PackageManifest, PackagePluginSpecs, PackageReleaseOutcome, PublishPluginPackage, PublishPluginSpec, ReleaseWorkspaceOptions, ResolvedPublishPlugin, ResumeWorkspaceReleaseOptions, ScopedPlugins, Workspace, WorkspaceDependency, WorkspacePackage, WorkspaceReleaseOutcome };

package/dist/index.d.ts

@@ -1,9 +1,6 @@
 import { AnalyzeCommitsContext, BranchSpec, Commit, GenerateNotesContext, ReleaseType } from "semantic-release";
 import { ReleaseGateState } from "@exadev/release-gate";
-//#region src/package-name.d.ts
 export declare const packageName = "@exadev/semantic-release-workspace";
-//#endregion
-//#region src/manifest.d.ts
 /**
  * The manifest fields that can name a workspace sibling.
  *
@@ -25,8 +22,6 @@ export declare function readManifest(path: string): Promise<PackageManifest>;
  * 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.
  */
 export declare function writeDependencyRange(path: string, field: DependencyField, dependency: string, range: string): Promise<void>;
-//#endregion
-//#region src/workspace.d.ts
 interface WorkspacePackage {
   readonly name: string;
   readonly version: string;
@@ -53,8 +48,6 @@ 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.
  */
 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. */
 interface WorkspaceDependency {
   /** The depending package's name. */
@@ -88,8 +81,6 @@ export declare function buildDependencyGraph(packages: readonly WorkspacePackage
 export declare function topologicalOrder(graph: DependencyGraph): readonly string[];
 /** The packages a release order names, in that order, for the stages that need each package's manifest rather than only its name. */
 export declare function orderedPackages(graph: DependencyGraph, order: readonly string[]): readonly WorkspacePackage[];
-//#endregion
-//#region src/version-range.d.ts
 /**
  * What happens to one dependency range when the sibling it points at releases a new version.
  *
@@ -131,8 +122,6 @@ export declare function classifyDependencyRange(current: string): DependencyRang
  * 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.
  */
 export declare function updateDependencyRange(current: string, version: string): DependencyRangeUpdate;
-//#endregion
-//#region src/bundling.d.ts
 /**
  * Which of a package's workspace dependencies ship inside its published artefact, as far as release types are concerned. Built by `resolveBundledDependencies`.
  */
@@ -156,8 +145,6 @@ interface BundledDependencies {
  * `bundlingPackages` names public workspace packages whose builds bundle their workspace `devDependencies`; `undefined` or an empty list leaves every package's release type as it was. Returns one entry per package in the graph. Throws `ReleaseConfigurationError` when a name is not a package in the workspace, or names a private package, which never publishes and so ships nothing to consumers.
  */
 export declare function resolveBundledDependencies(graph: DependencyGraph, bundlingPackages: readonly string[] | undefined): ReadonlyMap<string, BundledDependencies>;
-//#endregion
-//#region src/plugins.d.ts
 /**
  * One workspace dependency range that changed because its package released a new version during this run. `rewritten` means the dependent's manifest was edited on disk; `resolved-at-publish` means a bare `workspace:^`-style range whose on-disk text is unchanged. Both count towards the dependent's release.
  */
@@ -248,8 +235,6 @@ export declare function resolveWorkspacePublishPlugins(packages: readonly Publis
   readonly requireGitPlugin: boolean;
   readonly forbidGitPlugin?: boolean;
 }): ReadonlyMap<string, readonly ResolvedPublishPlugin[]>;
-//#endregion
-//#region src/gate-publish.d.ts
 /**
  * One package's outcome from a gated (`gatePublish: true`) detach pass -- what `resumeWorkspaceRelease` needs later to finish publishing it. `relativeDirectory`, not the absolute `directory`, is what a resume pass actually uses to resolve `cwd`: a resume can run against a different checkout of the same repository (a separate CI job, a separate clone) at a different absolute path, and `relativeDirectory` is the portable part.
  */
@@ -272,8 +257,6 @@ 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.
  */
 export declare function resumeWorkspaceRelease(options: ResumeWorkspaceReleaseOptions): Promise<WorkspaceReleaseOutcome>;
-//#endregion
-//#region src/release.d.ts
 /**
  * How a run commits its released changes:
  *
@@ -366,8 +349,6 @@ 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.
  */
 export declare function releaseWorkspace(options?: ReleaseWorkspaceOptions): Promise<WorkspaceReleaseOutcome>;
-//#endregion
-//#region src/errors.d.ts
 /**
  * Every failure this package raises deliberately is one of these, so a caller (or the CLI) can tell an orchestration failure it should report cleanly apart from an unexpected crash it should let propagate with a stack trace.
  *
@@ -395,5 +376,4 @@ export declare class GitCommandError extends WorkspaceReleaseError {
 }
 /** 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. */
 export declare class WorkspaceStateError extends WorkspaceReleaseError {}
-//#endregion
 export type { AppliedDependencyBump, BundledDependencies, CommitStrategy, DependencyBump, DependencyBumpSource, DependencyField, DependencyGraph, DependencyRangeShape, DependencyRangeUpdate, DetachedPackageRelease, PackageManifest, PackagePluginSpecs, PackageReleaseOutcome, PublishPluginPackage, PublishPluginSpec, ReleaseWorkspaceOptions, ResolvedPublishPlugin, ResumeWorkspaceReleaseOptions, ScopedPlugins, Workspace, WorkspaceDependency, WorkspacePackage, WorkspaceReleaseOutcome };

package/dist/index.js

@@ -10,10 +10,9 @@ import { generateNotes } from "@semantic-release/release-notes-generator";
 import semanticRelease from "semantic-release";
 import { pathToFileURL } from "node:url";
 import { detachRelease, resumeRelease } from "@exadev/release-gate";
-//#region src/package-name.ts
+// src/package-name.ts
 const packageName = "@exadev/semantic-release-workspace";
-//#endregion
-//#region src/errors.ts
+// src/errors.ts
 /**
 * Every failure this package raises deliberately is one of these, so a caller (or the CLI) can tell an orchestration failure it should report cleanly apart from an unexpected crash it should let propagate with a stack trace.
 *
@@ -56,8 +55,7 @@ var PnpmCommandError = class extends WorkspaceReleaseError {
 		super(`pnpm install --lockfile-only failed in ${cwd}: ${detail}`);
 	}
 };
-//#endregion
-//#region src/exec-file.ts
+// src/exec-file.ts
 /**
 * A hand-written promise wrapper around `child_process.execFile`, in place of `util.promisify(execFile)`: `execFile` synchronously returns a `ChildProcess` in addition to invoking its callback, which trips `@typescript-eslint/strict-void-return` when the whole function is handed to `promisify` (a value-returning function used where a void-returning one is contextually expected there) -- exactly the void-return contravariance leniency that rule exists to catch, even though `tsc` itself accepts the pattern. Calling `execFile` directly with our own callback, whose own return type really is `void`, sidesteps the mismatch instead of suppressing it.
 */
@@ -79,8 +77,7 @@ async function execFile$1(command, args, options) {
 		});
 	});
 }
-//#endregion
-//#region src/git.ts
+// src/git.ts
 /** Separates one commit's record in `git log --format` output. Chosen from the C0 control range so it can never appear in a hash or a file path. */
 const COMMIT_RECORD_SEPARATOR = "";
 /** The identity semantic-release's own core writes release commits under in CI when nothing else is configured (its COMMIT_NAME/COMMIT_EMAIL constants); dependency-bump commits use the same fallback so every commit a release run produces has a consistent author when the repository declares none. */
@@ -321,8 +318,7 @@ function toGitCommandError(args, cwd, cause) {
 	const stderr = cause instanceof Error && "stderr" in cause && typeof cause.stderr === "string" ? cause.stderr.trim() : "";
 	return new GitCommandError(args, cwd, exitCode, stderr !== "" ? stderr : cause instanceof Error ? cause.message : String(cause));
 }
-//#endregion
-//#region src/json.ts
+// src/json.ts
 function isJsonObject(value) {
 	return typeof value === "object" && value !== null && !Array.isArray(value);
 }
@@ -346,8 +342,7 @@ function stringifyJsonLike(value, originalText) {
 	const serialised = JSON.stringify(value, null, detectIndent(originalText));
 	return originalText.endsWith("\n") ? `${serialised}\n` : serialised;
 }
-//#endregion
-//#region src/manifest.ts
+// src/manifest.ts
 const DEPENDENCY_FIELDS = [
 	"dependencies",
 	"devDependencies",
@@ -397,8 +392,7 @@ async function writeDependencyRange(path, field, dependency, range) {
 	declared[dependency] = range;
 	await writeFile(path, stringifyJsonLike(parsed, text), "utf8");
 }
-//#endregion
-//#region src/workspace.ts
+// src/workspace.ts
 /** The one filename pnpm recognises as a workspace definition. */
 const WORKSPACE_MANIFEST = "pnpm-workspace.yaml";
 /** Never treat an installed dependency's own manifest as a workspace package, however permissive the configured globs are. pnpm applies the same exclusion. */
@@ -478,8 +472,7 @@ function trimTrailingSlashes(pattern) {
 function toPosix(path) {
 	return sep === "/" ? path : path.split(sep).join("/");
 }
-//#endregion
-//#region src/version-range.ts
+// src/version-range.ts
 const WORKSPACE_PROTOCOL = "workspace:";
 const CATALOG_PROTOCOL = "catalog:";
 const NPM_ALIAS_PROTOCOL = "npm:";
@@ -556,8 +549,7 @@ function updateDependencyRange(current, version) {
 		range: shape.workspacePrefixed ? `${WORKSPACE_PROTOCOL}${rewritten}` : rewritten
 	};
 }
-//#endregion
-//#region src/publishable-dependencies.ts
+// src/publishable-dependencies.ts
 /**
 * Throws `UnsupportedDependencyRangeError` unless every publishable package's installed dependencies (`dependencies`, `peerDependencies`, `optionalDependencies`) are ranges a consumer's package manager can resolve.
 *
@@ -577,8 +569,7 @@ function assertPublishableDependencies(packages) {
 	}
 	if (offences.length > 0) throw new UnsupportedDependencyRangeError(`Refusing to release: npm publish ships these dependency specifiers unchanged, so the published package could not be installed.\n${offences.join("\n")}\nDeclare a plain version range instead (for example "^1.2.3"). For a sibling in this workspace, keep "linkWorkspacePackages: true" in pnpm-workspace.yaml so pnpm still links it locally; this tool rewrites the range whenever the sibling releases. Packages marked "private" are never published and are exempt.`);
 }
-//#endregion
-//#region src/graph.ts
+// src/graph.ts
 /**
 * Builds the inter-package dependency graph from the manifests alone.
 *
@@ -676,8 +667,7 @@ function mustGet(map, key, what) {
 	if (value === void 0) throw new WorkspaceReleaseError(`Internal error: ${what} "${key}" disappeared from the dependency graph mid-run.`);
 	return value;
 }
-//#endregion
-//#region src/bundling.ts
+// src/bundling.ts
 /**
 * Validates `bundlingPackages` against the workspace and works out, for every package, which workspace dependencies it bundles.
 *
@@ -708,8 +698,7 @@ function resolveBundledDependencies(graph, bundlingPackages) {
 function isPrivateRuntimeEdge(edge, graph) {
 	return edge.field !== "devDependencies" && mustGet(graph.packages, edge.dependency, "package").private;
 }
-//#endregion
-//#region src/release-type.ts
+// src/release-type.ts
 /** Every release type semantic-release knows, highest first: the order `@semantic-release/commit-analyzer` itself ranks them in (its `lib/default-release-types.js`), so comparing two types here agrees with how the analyzer picks the highest type among a package's own commits. */
 const RELEASE_TYPES_HIGHEST_FIRST = [
 	"major",
@@ -735,8 +724,7 @@ function highestReleaseType(types) {
 function raiseReleaseType(base, other) {
 	return other === void 0 || RELEASE_TYPES_HIGHEST_FIRST.indexOf(base) <= RELEASE_TYPES_HIGHEST_FIRST.indexOf(other) ? base : other;
 }
-//#endregion
-//#region src/dependency-bump-commit.ts
+// src/dependency-bump-commit.ts
 /**
 * The commit message format for a cross-package dependency-range bump, shared between the code that writes it (`bumpDependents` in `release.ts`) and the code that reads it back (`createScopedPlugins` in `plugins.ts`).
 *
@@ -776,8 +764,7 @@ function matchTrailerLine(message, key) {
 	const line = message.split("\n").find((candidate) => candidate.startsWith(prefix));
 	return line === void 0 ? void 0 : line.slice(prefix.length).trim();
 }
-//#endregion
-//#region src/plugins.ts
+// src/plugins.ts
 /** The one plugin a private package is kept off by default: see `resolveWorkspacePublishPlugins` for why a package that never reaches a registry does not get a public GitHub Release either. */
 const GITHUB_RELEASE_PLUGIN = "@semantic-release/github";
 /** semantic-release's own `getLastRelease` returns `{}` for a package with no prior tag -- not `undefined`, and not a fully-populated `LastRelease` -- contradicting the `gitHead: string` its own type declares. Narrows structurally rather than trusting that declared type, so a first-release context's `lastRelease` (correctly, at runtime) never claims a `gitHead` it does not have. */
@@ -990,8 +977,7 @@ async function releasePackageAcrossBranchMoves(name, branch, attempt, log) {
 		log(`${name}: reported no release while the branch moved from ${tipBefore} to ${tipAfter}, which is also what a stale branch looks like; integrating and releasing it again.`);
 	}
 }
-//#endregion
-//#region src/pnpm.ts
+// src/pnpm.ts
 /**
 * Regenerates `pnpm-lock.yaml` for the whole workspace from the manifests currently on disk, without touching `node_modules` or installing anything -- the same lockfile-refresh step a contributor runs by hand after editing a `package.json` dependency range.
 *
@@ -1021,8 +1007,7 @@ function validateTagFormat(tagFormat) {
 function formatTagForPackage(tagFormat, name) {
 	return tagFormat.replaceAll("${name}", name);
 }
-//#endregion
-//#region src/single-commit-release.ts
+// src/single-commit-release.ts
 /**
 * `commitStrategy: 'single'`: one combined commit for the whole run instead of one commit per package release plus one per dependency bump.
 *
@@ -1368,8 +1353,7 @@ async function loadReleasePlugin(absolutePath, cache) {
 	cache.set(absolutePath, loaded);
 	return loaded;
 }
-//#endregion
-//#region src/gate-publish.ts
+// src/gate-publish.ts
 /**
 * The `gatePublish: true` half of `releaseWorkspace`: tags and pushes every due package via `@exadev/release-gate`'s `detachRelease`, but never publishes. Built on the same `runReleaseLoop` the normal per-package path uses, so dependency-range bumps between packages happen identically either way -- only the release call itself (`detachRelease` instead of `semanticRelease`) and how "did it release" gets read differ.
 */
@@ -1511,8 +1495,7 @@ async function resumeWorkspaceRelease(options) {
 		packages
 	};
 }
-//#endregion
-//#region src/release.ts
+// src/release.ts
 /**
 * Releases every package in a pnpm workspace with independent versions, in dependency order.
 *
@@ -1721,5 +1704,4 @@ function branchTracker(workspace, log) {
 		tip: async () => await fetchBranchTip(await currentBranch({ cwd: workspace.root }), { cwd: workspace.root })
 	};
 }
-//#endregion
 export { DEFAULT_PUBLISH_PLUGINS, DependencyCycleError, GitCommandError, ReleaseConfigurationError, SINGLE_COMMIT_DEFAULT_PUBLISH_PLUGINS, UnsupportedDependencyRangeError, WorkspaceDiscoveryError, WorkspaceReleaseError, WorkspaceStateError, buildDependencyGraph, classifyDependencyRange, createScopedPlugins, discoverWorkspace, filterCommitsToDirectory, orderedPackages, packageName, readManifest, releaseWorkspace, resolveBundledDependencies, resolvePublishPlugins, resolveWorkspacePublishPlugins, resumeWorkspaceRelease, topologicalOrder, updateDependencyRange, writeDependencyRange };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@exadev/semantic-release-workspace",
-  "version": "3.2.16",
+  "version": "3.2.18",
   "description": "Independent per-package semantic-release orchestration for pnpm workspaces, without lockstep versioning.",
   "type": "module",
   "repository": {