hermex 2.0.2 → 2.1.0

package/dist/index.d.mts

@@ -256,7 +256,7 @@ type ReleaseAgeConfig = HermexConfig['releaseAge'];
 type ReleaseAgeThresholds = HermexConfig['releaseAge']['thresholds'];
 //#endregion
 //#region src/npm-registry/types.d.ts
-type UpgradeLevel = 'needs_upgrade' | 'mandatory_upgrade';
+type UpgradeLevel = 'minor_overdue' | 'major_overdue';
 type SemverBump = 'patch' | 'minor' | 'major';
 interface AvailableUpgrade {
   version: string;
@@ -285,10 +285,11 @@ interface ReleaseAgeEntry {
   installedVersion: string;
   upgrades: AvailableUpgrade[];
   /**
-   * `null` when compliant, including when no release newer than
-   * `installedVersion` has ever fallen inside its bump tier's threshold —
-   * in that case the only achievable target is `latestVersion` itself, so
-   * there's nothing avoidably stale to flag (#26).
+   * `null` only when there are no breached upgrades at all. Independent of
+   * whether `minCompliantVersion` fell back to `latestVersion` — a package
+   * can still be overdue on a breached tier even when latest itself is past
+   * that tier's threshold and there's nothing fresher to recommend instead
+   * (#29).
    */
   worstLevel: UpgradeLevel | null;
   pendingUpgrade?: PendingUpgrade;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "hermex",
-  "version": "2.0.2",
+  "version": "2.1.0",
   "description": "SWC-based AST parser for analyzing code and React component usage patterns across entire codebases",
   "keywords": [
     "analysis",