@rtorcato/repo-tooling 3.0.0 → 3.2.0

package/dist/cli/commands/doctor.js

@@ -5,10 +5,11 @@ import { resolveLanguageModule } from '../../languages/registry.js';
 import { SWIFT_GIT_HOOKS, runSwiftChecks } from '../../languages/swift/checks.js';
 import { detectLanguage } from '../utils/detect-language.js';
 import { checkGitHubSettings } from '../../base/github-settings.js';
+import { checkGitIdentity } from '../../base/git-identity.js';
 import { LOCKFILE_VERSION, readLockfile } from '../utils/lockfile.js';
 import { declinedInLock, getFixTargetForCheck } from './fix-targets.js';
 import { checkAiSetup, checkCodeowners, checkCodeQL, checkCommunityHealth, checkCoverageUpload, checkDependabot, checkEditorConfig, checkFile, checkGitHooks, checkGitHubActions, checkGitLabCI, checkPrePushHook, checkReadmeBadges, COMMITLINT_FILE_CHECK, } from '../../base/checks.js';
-import { allDeps, checkAreTheTypesWrong, checkDocsSite, checkEnginesNode, checkKnip, checkLintStaged, checkNodeVersionConsistency, checkNodeVersionPin, checkPackageJson, checkPublint, checkSemanticRelease, checkSizeLimit, checkTailwind, checkPnpmWorkspace, checkTreeshakeSetup, checkTurborepo, checkTypedoc, checkVerifyScript, checkVscodeExtensions, evaluateNodeVersion, FILE_CHECKS, findDocsAppDir, jsBadgeAudience, jsGitHooksProfile, readPackageJson, } from '../../languages/js/checks.js';
+import { allDeps, checkAreTheTypesWrong, checkConfigSchemaVersions, checkDocsSite, checkEnginesNode, checkGitDependencies, checkKnip, checkLintStaged, checkNodeVersionConsistency, checkNodeVersionPin, checkPackageJson, checkPublint, checkSemanticRelease, checkSizeLimit, checkTailwind, checkPnpmWorkspace, checkTreeshakeSetup, checkTurborepo, checkTypedoc, checkVerifyScript, checkVscodeExtensions, evaluateNodeVersion, FILE_CHECKS, findDocsAppDir, jsBadgeAudience, jsGitHooksProfile, readPackageJson, } from '../../languages/js/checks.js';
 export { evaluateNodeVersion };
 const PACKAGE = '@rtorcato/repo-tooling';
 // Detects the broken-release-on-protected-main footgun: a workflow that runs
@@ -140,6 +141,7 @@ function demoteDeclined(results, lock) {
 async function runBaseChecks(dir, lock, opts) {
     const results = [];
     results.push(checkLockfile(lock));
+    results.push(await checkGitIdentity(dir));
     results.push(await checkEditorConfig(dir));
     results.push(await checkFile(dir, COMMITLINT_FILE_CHECK));
     if (opts.hooks) {
@@ -216,6 +218,8 @@ export async function runDoctor(dir) {
     results.push(evaluateNodeVersion(process.version));
     results.push(checkPackageJson(pkg));
     results.push(checkEnginesNode(pkg));
+    results.push(await checkConfigSchemaVersions(targetDir, pkg));
+    results.push(checkGitDependencies(pkg));
     results.push(await checkVscodeExtensions(targetDir));
     results.push(await checkNodeVersionPin(targetDir));
     results.push(await checkNodeVersionConsistency(targetDir, pkg));

package/dist/languages/js/checks.js

@@ -947,3 +947,161 @@ export async function checkTailwind(dir, pkg) {
         hint: 'Run `npx @rtorcato/repo-tooling fix tailwind` to scaffold the v4 PostCSS wiring',
     };
 }
+/**
+ * Both checks below read `package.json` alone — no network, no lockfile. They
+ * report `optional-missing` rather than `drift`: each is a policy call a repo
+ * can legitimately decide against, so they surface in doctor's output and can
+ * be declined in `.repo-tooling.json`, but neither fails a build.
+ */
+/** `[major, minor, patch]` floor of a range, or null when it hasn't got one. */
+export function rangeFloor(range) {
+    const m = /^[\s^~>=<v]*(\d+)\.(\d+)\.(\d+)/.exec(range);
+    return m ? [Number(m[1]), Number(m[2]), Number(m[3])] : null;
+}
+/**
+ * Major.minor only — patch is deliberately ignored. New config keys and new
+ * behaviour arrive in minors; a dev floor five patches above the peer floor
+ * (`^2.5.0` vs `^2.5.5`) is just a routine bump and flagging it would make
+ * this check fire on almost every package.
+ */
+function compareFloor(a, b) {
+    return a[0] - b[0] || a[1] - b[1];
+}
+/**
+ * Config files whose `$schema` URL carries the tool version the config is
+ * written for, and the package that reads them. One entry per tool; adding
+ * another is a line here.
+ */
+const SCHEMA_CONFIGS = [
+    { files: ['biome.json', 'biome.jsonc'], host: 'biomejs.dev', pkg: '@biomejs/biome' },
+];
+/** The version out of `https://biomejs.dev/schemas/2.5.0/schema.json`. */
+export function schemaUrlVersion(url) {
+    const m = /\/(\d+\.\d+\.\d+)\//.exec(url);
+    return m?.[1] ? rangeFloor(m[1]) : null;
+}
+/**
+ * `"$schema": "..."` without parsing the file. Biome configs may be JSONC, and
+ * a comment is enough to break `JSON.parse` — the one field this needs is
+ * cheaper and safer to read directly.
+ */
+function readSchemaUrl(contents) {
+    return /"\$schema"\s*:\s*"([^"]+)"/.exec(contents)?.[1] ?? null;
+}
+/**
+ * A shipped config written for a newer tool version than the package claims to
+ * support (#330). The `$schema` URL is an explicit, machine-readable statement
+ * of which version the config targets, so comparing it against the declared
+ * dependency floor is exact — no heuristics, no false positives.
+ *
+ * This is the #330 defect precisely: `tooling/biome/biome.json` carries
+ * `$schema` 2.5.0 and uses `linter.rules.preset`, a 2.5 key, while
+ * `peerDependencies` advertised `@biomejs/biome: ^2.0.0`. Consumers on 2.0–2.4
+ * got `Found an unknown key \`preset\`` with nothing pointing at the range.
+ *
+ * It reads the same way in a consuming repo: a `biome.json` targeting 2.5.0
+ * with `@biomejs/biome: ^2.3.0` in devDependencies is the identical failure,
+ * one level down.
+ *
+ * The floor is what matters, not the ceiling — `^2.0.0` resolves to the newest
+ * 2.x today, so the repo's own install works and only consumers pinned lower
+ * break. That is exactly why this goes unnoticed.
+ */
+export async function checkConfigSchemaVersions(dir, pkg) {
+    const check = 'Config schema versions';
+    // peerDependencies is the contract a publisher offers; devDependencies is
+    // what a leaf repo actually installs. Prefer the former when present.
+    const declared = {
+        ...(pkg?.dependencies ?? {}),
+        ...(pkg?.devDependencies ?? {}),
+        ...(pkg?.peerDependencies ?? {}),
+    };
+    const mismatches = [];
+    let checked = 0;
+    for (const spec of SCHEMA_CONFIGS) {
+        for (const file of spec.files) {
+            const filepath = path.join(dir, file);
+            if (!(await fs.pathExists(filepath)))
+                continue;
+            const url = readSchemaUrl(await fs.readFile(filepath, 'utf8'));
+            if (!url?.includes(spec.host))
+                continue;
+            const schemaVersion = schemaUrlVersion(url);
+            const range = declared[spec.pkg];
+            if (!schemaVersion || !range)
+                continue;
+            const floor = rangeFloor(range);
+            if (!floor)
+                continue;
+            checked++;
+            if (compareFloor(schemaVersion, floor) > 0) {
+                const v = schemaVersion.join('.');
+                mismatches.push(`${file} targets ${spec.pkg} ${v} but the range is ${range}`);
+            }
+        }
+    }
+    if (checked === 0) {
+        return { check, status: 'ok', detail: 'no versioned config schemas to compare' };
+    }
+    if (mismatches.length === 0) {
+        return {
+            check,
+            status: 'ok',
+            detail: `${checked} config schema${checked === 1 ? '' : 's'} within the declared version range`,
+        };
+    }
+    return {
+        check,
+        status: 'optional-missing',
+        detail: `${mismatches.length} config${mismatches.length === 1 ? '' : 's'} written for a newer tool than declared: ${mismatches.join('; ')}`,
+        hint: 'Raise the dependency floor to the version the config targets, or rewrite the config for the oldest version supported. Anyone resolving below the schema version gets a config-parse error that never mentions the version range.',
+    };
+}
+/** npm git specifiers, including the bare `owner/repo` GitHub shorthand. */
+const GIT_PROTOCOL = /^(?:github|gitlab|bitbucket|gist):|^git\+|^git:\/\//;
+const GITHUB_SHORTHAND = /^[A-Za-z0-9][\w.-]*\/[A-Za-z0-9][\w.-]*(?:#.*)?$/;
+export function isGitSpecifier(spec) {
+    return GIT_PROTOCOL.test(spec) || GITHUB_SHORTHAND.test(spec);
+}
+/**
+ * A git dependency with no `#ref` (#332). The package manager resolves it once
+ * and pins the commit in the lockfile, so it never moves again until somebody
+ * re-resolves by hand — with no version mismatch, no Dependabot PR, and no
+ * signal of any kind that it has gone stale.
+ *
+ * This is how the docs homepage kept advertising `@rtorcato/js-tooling` for
+ * days after the rename: `github:rtorcato/shared-docs` had been pinned to a
+ * pre-rename commit and nothing could tell.
+ */
+export function checkGitDependencies(pkg) {
+    const check = 'Git dependencies';
+    const fields = ['dependencies', 'devDependencies', 'optionalDependencies'];
+    const refless = [];
+    let total = 0;
+    for (const field of fields) {
+        const deps = pkg?.[field] ?? {};
+        for (const [name, spec] of Object.entries(deps)) {
+            if (typeof spec !== 'string' || !isGitSpecifier(spec))
+                continue;
+            total++;
+            if (!spec.includes('#'))
+                refless.push(`${name} (${spec})`);
+        }
+    }
+    if (total === 0) {
+        return { check, status: 'ok', detail: 'no git dependencies' };
+    }
+    if (refless.length === 0) {
+        return {
+            check,
+            status: 'ok',
+            detail: `${total} git dependenc${total === 1 ? 'y' : 'ies'}, all with an explicit ref`,
+        };
+    }
+    return {
+        check,
+        status: 'optional-missing',
+        detail: `${refless.length} git dependenc${refless.length === 1 ? 'y' : 'ies'} with no ref — pinned to whatever commit was current at install time: ${refless.join('; ')}`,
+        hint: 'Prefer publishing to a registry and depending on a semver range. Failing that, add an explicit ref — `#semver:^1.2.0` is strongest, `#main` at least makes the intent legible and `pnpm update` meaningful.',
+    };
+}

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@rtorcato/repo-tooling",
-	"version": "3.0.0",
+	"version": "3.2.0",
 	"description": "One CLI to scaffold, audit and fix your repo's whole toolchain — linting, tests, commits, releases & CI.",
 	"type": "module",
 	"keywords": [

package/tooling/semantic-release/github.mjs

@@ -43,6 +43,13 @@ export default {
 			{
 				assets: ['CHANGELOG.md', 'package.json', 'README.md'],
 				message: 'chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}',
+				// Don't label the "release is failing" issue. The default is
+				// ['semantic-release'], and GitHub rejects issue creation outright when
+				// the label doesn't exist on the repo — so a failed release fails *again*
+				// with a 422 that buries the real error under an octokit stack trace.
+				// false keeps the issue (and its post-mortem) without requiring every
+				// consuming repo to pre-create a label.
+				labels: false,
 			},
 		],
 		[