@williamthorsen/release-kit 18.1.0 → 18.2.0

package/docs/configuration.md

@@ -143,7 +143,7 @@ Validation rules:
 - Full-tuple `(name, tagPrefix)` duplicates within `retiredPackages` are rejected.
 - Two entries sharing the same `tagPrefix` but different `name`s are accepted: Such a pair documents a package renamed within the repo before being retired.
 
-`show-tag-prefixes` currently does not render a dedicated "Retired packages" section (deferred). Declaring a retired entry is verifiable by confirming that its `tagPrefix` stops appearing under "Undeclared tag prefixes" in the `show-tag-prefixes` output.
+`show-tag-prefixes` lists each retired entry under "Retired packages", with its tag count and successor.
 
 ## Tag prefix collisions
 
@@ -160,13 +160,13 @@ The rule is enforced at config load; the resulting error identifies both collidi
 
 ## `release-kit show-tag-prefixes`
 
-Prints a per-workspace table of derived tag prefixes, tag counts, and declared legacy prefixes, with a row for each directory target. Also reports any release-shaped tag prefix in the repo that is neither a derived prefix nor declared via `legacyIdentities`, along with a copy-pasteable `workspaces: [...]` config snippet. The snippet uses a `TODO-fill-in-legacy-npm-name` placeholder for each identity's `name`; replace it with the package's prior npm name before pasting.
+Prints one block per workspace and directory target, titled with its path and its package name or `releases` key, with its derived tag prefix and each declared legacy identity, their tag counts, and a status. Prefixes and counts are aligned in columns across the whole output. A "Retired packages" section follows when the config declares `retiredPackages`. An "Undeclared tag prefixes" section always follows: It reports any release-shaped tag prefix in the repo that is neither derived nor declared, along with a copy-pasteable `workspaces: [...]` config snippet, or `(none)`. The snippet uses a `TODO-fill-in-legacy-npm-name` placeholder for each identity's `name`; replace it with the package's prior npm name before pasting. When a derived prefix does not have any tags yet, a closing note explains that `release-kit tag` creates the first tag from the tags file that `release-kit prepare` writes.
 
 Exits `0` when every workspace derives a prefix and the workspaces' prefixes don't collide; exits `1` on any derivation failure or collision. Undeclared candidates do not affect the exit code; the `legacy tag prefixes are declared` readyup check reports them as a warning.
 
 When a config file exists and either fails to load or fails schema validation, the command reports the failure on stderr and exits `1` without printing a preview, because a config that cannot be read leaves the declared-versus-undeclared verdict wrong in the one dimension on which the command exists to report. That holds on the default path and under `--config`, and in single-package mode as well as monorepo mode. An absent default config is a supported state and still previews against derived defaults.
 
-In single-package mode, prints a single row with `workspacePath = .` and `derivedPrefix = v`; legacy entries and undeclared-candidate scanning are not applicable.
+In single-package mode, prints a single block for `.` with the derived prefix `v`; legacy entries and undeclared-candidate scanning are not applicable.
 
 ## `VersionPatterns`
 

package/docs/labels.md

@@ -10,8 +10,6 @@ Manages GitHub label definitions via the `repoLabels` block of `.config/release-
 
 `init` and `generate` accept `--config <path>` to read a config elsewhere; `sync` reads none and rejects the flag. Under `--config`, `init` reads the named file and prints the block for manual paste, and fails when that file does not exist rather than scaffolding one, so its write target stays `.config/release-kit.config.ts`. See [Config file location](configuration.md#config-file-location).
 
-Every `sync-labels` subcommand refuses to run while the retired `.config/sync-labels.config.ts` is present, so that custom labels cannot be silently dropped mid-migration, and the refusal names what to move and where.
-
 ### Label configuration
 
 ```typescript

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@williamthorsen/release-kit",
-  "version": "18.1.0",
+  "version": "18.2.0",
   "description": "Version-bumping and changelog-generation toolkit for release workflows",
   "keywords": [
     "changelog",
@@ -51,9 +51,9 @@
     "templates"
   ],
   "dependencies": {
-    "@williamthorsen/change-grammar": "0.4.0",
-    "@williamthorsen/nmr-core": "0.16.1",
-    "@williamthorsen/toolbelt.errors": "0.9.1",
+    "@williamthorsen/change-grammar": "0.4.1",
+    "@williamthorsen/nmr-core": "0.16.2",
+    "@williamthorsen/toolbelt.errors": "0.10.1",
     "json-stringify-pretty-compact": "4.0.0",
     "semver": "7.8.6",
     "yaml": "2.9.1",
@@ -61,12 +61,13 @@
   },
   "devDependencies": {
     "@types/semver": "7.8.0",
-    "@williamthorsen/toolbelt.filesystem": "0.10.1",
-    "@williamthorsen/toolbelt.testing": "0.8.1",
-    "@williamthorsen/toolbelt.vitest": "0.13.3",
+    "@williamthorsen/nmr": "2.2.1",
+    "@williamthorsen/toolbelt.filesystem": "0.10.3",
+    "@williamthorsen/toolbelt.testing": "0.8.3",
+    "@williamthorsen/toolbelt.vitest": "0.13.5",
     "actionlint": "2.0.6",
     "esbuild": "0.28.2",
-    "readyup": "0.45.1",
+    "readyup": "0.46.2",
     "smol-toml": "1.9.1",
     "vitest": "5.1.0"
   },

package/dist/esm/sync-labels/retiredConfig.d.ts

@@ -1,11 +0,0 @@
-/** Path of the retired standalone sync-labels config file. */
-export declare const RETIRED_SYNC_LABELS_CONFIG_PATH = ".config/sync-labels.config.ts";
-/**
- * Reports an actionable migration error when the retired standalone config file is present.
- *
- * Returns `true` when the file exists, in which case the caller must abort. The check is
- * unconditional on config content: File presence alone triggers it, so a half-migrated
- * repo cannot silently lose its custom labels. `configPath` names the config into which the
- * message directs the labels.
- */
-export declare function checkRetiredSyncLabelsConfig(configPath?: string): boolean;

package/dist/esm/sync-labels/retiredConfig.js

@@ -1,12 +0,0 @@
-import { existsSync } from 'node:fs';
-import { reportError } from '@williamthorsen/nmr-core';
-import { BIN } from "../bin.js";
-import { CONFIG_FILE_PATH } from "../loadConfig.js";
-export const RETIRED_SYNC_LABELS_CONFIG_PATH = '.config/sync-labels.config.ts';
-export function checkRetiredSyncLabelsConfig(configPath = CONFIG_FILE_PATH) {
-    if (!existsSync(RETIRED_SYNC_LABELS_CONFIG_PATH)) {
-        return false;
-    }
-    reportError(BIN, `${RETIRED_SYNC_LABELS_CONFIG_PATH} is no longer read. Move its labels into the \`repoLabels\` block of ${configPath} (presets move to \`repoLabels.extends\`; each label becomes a \`'name': { color, description }\` entry under \`repoLabels.labels\`), then delete the file.`);
-    return true;
-}