rman 2.13.0 → 2.15.0

package/core/interfaces/plugin.d.ts

@@ -4,6 +4,7 @@ import type { BinPath } from '../../utils/bin-path.js';
 import type { RmanApplication } from '../application.js';
 import type { Repository } from '../classes/repository.js';
 import type { Workspace } from '../classes/workspace.js';
+import type { DependencyUpdater } from './dependency-updater.js';
 import type { ManifestProvider } from './manifest.js';
 /**
  * **One technology, as a whole** - Node, Cargo, Maven. Everything rman needs in order to treat a
@@ -75,6 +76,9 @@ export interface Platform {
     /** How this technology's releases are planned - where a package's change boundary comes from
      *  when it has no release tag, and how far into its group a bump reaches. */
     versionPlanner?: VersionPlanService;
+    /** How this technology's dependencies are checked against their registry and moved forward -
+     *  what `rman deps` asks. Absent, `deps` leaves this technology's packages alone. */
+    dependencyUpdater?: DependencyUpdater;
 }
 /**
  * **A plugin is whatever a package contributes; a platform is one of the things it can contribute.**
@@ -168,7 +172,7 @@ export declare function isPlugin(value: unknown): value is Plugin;
  * - no `getBinPaths` -> nothing is prepended to a child process's PATH, so the inherited one
  *   stands on its own rather than being guessed at;
  * - no `getRunSteps` -> a package's steps come from its `.rmanrc` alone, the core's only source;
- * - no `versionPlanner` -> `version`/`changed` fail naming the key, rather than releasing a
+ * - no `versionPlanner` -> `version` fails naming the key, rather than releasing a
  *   plausible but untrue set of packages from a default nobody chose.
  */
 export declare const basePlatform: Platform;

package/core/interfaces/plugin.js

@@ -73,7 +73,7 @@ export function isPlugin(value) {
  * - no `getBinPaths` -> nothing is prepended to a child process's PATH, so the inherited one
  *   stands on its own rather than being guessed at;
  * - no `getRunSteps` -> a package's steps come from its `.rmanrc` alone, the core's only source;
- * - no `versionPlanner` -> `version`/`changed` fail naming the key, rather than releasing a
+ * - no `versionPlanner` -> `version` fails naming the key, rather than releasing a
  *   plausible but untrue set of packages from a default nobody chose.
  */
 export const basePlatform = definePlatform({

package/index.d.ts

@@ -65,6 +65,8 @@ export { Manifest } from './core/interfaces/manifest.js';
 export { Registry } from './core/classes/registry.js';
 export { Repository } from './core/classes/repository.js';
 export { Service, type ServiceFactory, type ServiceMap } from './core/classes/service.js';
+/** The `deps` seam: how a technology checks its dependencies against a registry and moves them. */
+export { DependencyUpdater } from './core/interfaces/dependency-updater.js';
 export { declaredTargets, type PublishTarget, shipsTo, skipReasonFor, targetsOf, unknownTargets, } from './core/interfaces/publish-target.js';
 export type { RunConditionFn, RunStepContext, RunStepFn, RunStepObject, RunStepValue, } from './core/interfaces/run-step.js';
 /**

package/index.js

@@ -71,6 +71,8 @@ export { Manifest } from './core/interfaces/manifest.js';
 export { Registry } from './core/classes/registry.js';
 export { Repository } from './core/classes/repository.js';
 export { Service } from './core/classes/service.js';
+/** The `deps` seam: how a technology checks its dependencies against a registry and moves them. */
+export { DependencyUpdater } from './core/interfaces/dependency-updater.js';
 export { declaredTargets, shipsTo, skipReasonFor, targetsOf, unknownTargets, } from './core/interfaces/publish-target.js';
 export { basePlatform, definePlatform, definePlugin, isPlatform, } from './core/interfaces/plugin.js';
 /** The numbering seam. `VersionScheme` is abstract - `highestVersion`/`highestBump`/`smallestBump`

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "rman",
   "description": "Repository manager",
-  "version": "2.13.0",
+  "version": "2.15.0",
   "author": "Panates",
   "license": "MIT",
   "dependencies": {

package/services/change-hash.service.d.ts

@@ -106,8 +106,8 @@ export declare namespace ChangeHashService {
      * `changelog --from` uses, but reusable anywhere a command wants to answer "what changed for this
      * package". An explicit `options.from` (anything but `AUTO`) is returned as-is, applying the same
      * way to every package. Otherwise, it's auto-detected in order: (1) this package's own most recent
-     * release tag - the same network-free `findLatestTag` lookup `version`/`changed` themselves use,
-     * so all three commands agree on "since when" for any repo whose tags are the ones `rman version`
+     * release tag - the same network-free `findLatestTag` lookup `version` itself uses,
+     * so both commands agree on "since when" for any repo whose tags are the ones `rman version`
      * actually created; (2) failing that (no tag at all yet - e.g. onboarding `rman` onto a repo with
      * real release history but no `rman`-created tags), whatever this package's **own ecosystem**
      * reports as its published version (`Plugin.publishedVersion`), mapped to a git tag via

package/services/change-hash.service.js

@@ -134,8 +134,8 @@ export var ChangeHashService;
      * `changelog --from` uses, but reusable anywhere a command wants to answer "what changed for this
      * package". An explicit `options.from` (anything but `AUTO`) is returned as-is, applying the same
      * way to every package. Otherwise, it's auto-detected in order: (1) this package's own most recent
-     * release tag - the same network-free `findLatestTag` lookup `version`/`changed` themselves use,
-     * so all three commands agree on "since when" for any repo whose tags are the ones `rman version`
+     * release tag - the same network-free `findLatestTag` lookup `version` itself uses,
+     * so both commands agree on "since when" for any repo whose tags are the ones `rman version`
      * actually created; (2) failing that (no tag at all yet - e.g. onboarding `rman` onto a repo with
      * real release history but no `rman`-created tags), whatever this package's **own ecosystem**
      * reports as its published version (`Plugin.publishedVersion`), mapped to a git tag via

package/services/system-info.d.ts

@@ -7,6 +7,9 @@ export declare namespace SystemInfo {
         version: string;
         root: string;
         packageCount: number;
+        /** The technologies this run loaded, by `Platform.name`, in the order a directory is offered to
+         *  them - so `["cargo", "node"]` means a directory both recognize is a Cargo package. */
+        platforms: string[];
     }
     /** Whatever `envinfo` reports, grouped by category - shape is `envinfo`'s own, not ours. */
     type SystemInfo = Record<string, Record<string, unknown>>;

package/services/system-info.js

@@ -23,6 +23,7 @@ export var SystemInfo;
             version: repository.rootPackage.version,
             root: repository.dirname,
             packageCount: repository.getPackages().length,
+            platforms: [...repository.app.platforms].map(p => p.name),
         };
     }
     SystemInfo.getRepositoryInfo = getRepositoryInfo;

package/services/version-plan.service.d.ts

@@ -56,7 +56,8 @@ export declare abstract class VersionPlanService {
      * Across groups: a package depending on another group's bumped package always gets its scheme's
      * **smallest** bump of its own (never inheriting the source's) - the dependency reference itself
      * is the only thing that changed for it. Whether that re-triggers its own group's cascade is
-     * `cascade`'s answer for that smallest bump (`'changed'` under npm, so it does not), but it can
+     * `cascade`'s answer for that smallest bump (`'dependents'` under npm, so its own in-group
+     * dependents move with it), and it can
      * itself ripple into a third group, and so on, until nothing new is affected - see
      * `rippleCrossGroup`.
      *

package/services/version-plan.service.js

@@ -58,7 +58,8 @@ export class VersionPlanService {
      * Across groups: a package depending on another group's bumped package always gets its scheme's
      * **smallest** bump of its own (never inheriting the source's) - the dependency reference itself
      * is the only thing that changed for it. Whether that re-triggers its own group's cascade is
-     * `cascade`'s answer for that smallest bump (`'changed'` under npm, so it does not), but it can
+     * `cascade`'s answer for that smallest bump (`'dependents'` under npm, so its own in-group
+     * dependents move with it), and it can
      * itself ripple into a third group, and so on, until nothing new is affected - see
      * `rippleCrossGroup`.
      *
@@ -174,8 +175,8 @@ export class VersionPlanService {
          * The abort case, marked **after** the root entry so the whole table reads as one coherent
          * "if this were committed" preview rather than a mixture of two.
          *
-         * `to` survives the overwrite; `status` is what every writer filters on (`VersionService`,
-         * `changed`), so an `'error'` entry carrying a version cannot be applied by any of them - and
+         * `to` survives the overwrite; `status` is what every writer filters on (`VersionService`),
+         * so an `'error'` entry carrying a version cannot be applied by any of them - and
          * `version` throws on the first error before it would reach `applyPlan` anyway. The reason
          * keeps the boundary it was computed from, because the status column already says `error` and
          * a reader losing `changed since <tag>` loses the only thing that explains the number.
@@ -523,8 +524,9 @@ export class VersionPlanService {
     function getPlanner(app) {
         const planner = app.versionPlanner;
         if (!planner) {
-            throw new Error('No version planner is registered, so no version plan can be computed. Name a plugin that ' +
-                'contributes one in .rmanrc "plugins" - "rman-node" for a Node repository.');
+            throw new Error('No version planner is registered, so no version plan can be computed. Name a technology ' +
+                'that contributes one in .rmanrc "platforms", or reach it through "extends" - "rman:node" ' +
+                'for a Node repository, which is laid down by default unless presets were turned off.');
         }
         return planner;
     }

package/services/version.service.js

@@ -361,8 +361,8 @@ export class VersionService extends Service {
                     (pkg.provider
                         ? `  The "${pkg.provider}" provider looked and found no version to change. Name the ` +
                             `identifier with { file, constant } if it is not "version", or drop the entry.`
-                        : `  This package belongs to no ecosystem (no plugin claimed it), so nothing knows how ` +
-                            `a version is declared in it. Name a plugin in .rmanrc "plugins".`));
+                        : `  This package belongs to no ecosystem (no platform claimed it), so nothing knows how ` +
+                            `a version is declared in it. Name the technology in .rmanrc "platforms", or reach it through "extends" (e.g. "rman:node").`));
             }
             /** Matched, but already reads the target - nothing to write and nothing to report. Distinct
              *  from the `undefined` above, which is "nothing here to rewrite at all". */
@@ -447,8 +447,8 @@ function assertStampable(pkg, version) {
             (pkg.provider
                 ? `  The "${pkg.provider}" provider looked and found no version to change. Name the ` +
                     `identifier with { file, constant } if it is not "version", or drop the entry.`
-                : `  This package belongs to no ecosystem (no plugin claimed it), so nothing knows how a ` +
-                    `version is declared in it. Name a plugin in .rmanrc "plugins".`));
+                : `  This package belongs to no ecosystem (no platform claimed it), so nothing knows how a ` +
+                    `version is declared in it. Name the technology in .rmanrc "platforms", or reach it through "extends" (e.g. "rman:node").`));
     }
 }
 /**

package/utils/package-filter.d.ts

@@ -176,7 +176,7 @@ applySkip?: boolean): Package[];
  * **It only means anything where a command scopes by the current directory** - `run`/`build`/`test`,
  * `exec`, `clean`, `changelog` and `diff` narrow to `Repository.currentPackage` when you stand
  * inside a package, and this is the escape hatch. On a command that already works across the whole
- * repository (`version`, `publish`, `list`, `changed`) it would be a flag that does nothing, which
+ * repository (`version`, `publish`, `list`) it would be a flag that does nothing, which
  * is worse than not offering it: a no-op flag reads as a promise.
  *
  * That same rule is why there is no `--root-only` beside it, however naturally the pair reads: it

package/utils/package-filter.js

@@ -210,7 +210,7 @@ applySkip = true) {
  * **It only means anything where a command scopes by the current directory** - `run`/`build`/`test`,
  * `exec`, `clean`, `changelog` and `diff` narrow to `Repository.currentPackage` when you stand
  * inside a package, and this is the escape hatch. On a command that already works across the whole
- * repository (`version`, `publish`, `list`, `changed`) it would be a flag that does nothing, which
+ * repository (`version`, `publish`, `list`) it would be a flag that does nothing, which
  * is worse than not offering it: a no-op flag reads as a promise.
  *
  * That same rule is why there is no `--root-only` beside it, however naturally the pair reads: it