@effected/workspaces 0.16.0 → 0.17.0

package/WorkspaceCatalogs.js

@@ -444,7 +444,8 @@ var WorkspaceCatalogs = class WorkspaceCatalogs extends Context.Service()("@effe
 			}),
 			importerVersions: Effect.fn("WorkspaceCatalogs.importerVersions")(function* () {
 				return (yield* memo).importerVersions;
-			})
+			}),
+			refresh: () => invalidate
 		};
 	});
 	/**
@@ -509,6 +510,11 @@ var WorkspaceCatalogs = class WorkspaceCatalogs extends Context.Service()("@effe
 	* the importer index from the lockfile's importer blocks — neither is in a
 	* `CatalogSet`) and always die unless stubbed.
 	*
+	* `refresh` defaults to `Effect.void` honestly: the double holds no memo,
+	* so "drop the memoized assembly" is genuinely a no-op — the stubs answer
+	* fresh on every call already. This mirrors `WorkspaceDiscovery.makeTest`'s
+	* `refresh`.
+	*
 	* @example
 	* ```ts
 	* import { CatalogSet, WorkspaceCatalogs } from "@effected/workspaces";
@@ -528,6 +534,7 @@ var WorkspaceCatalogs = class WorkspaceCatalogs extends Context.Service()("@effe
 			peerDependencyRules: () => unstubbed("peerDependencyRules"),
 			releaseAgeGate: () => unstubbed("releaseAgeGate"),
 			importerVersions: () => unstubbed("importerVersions"),
+			refresh: () => Effect.void,
 			...overrides
 		};
 	};

package/index.d.ts

@@ -2449,6 +2449,26 @@ interface WorkspaceCatalogsShape {
    * nothing rather than failing.
    */
   readonly importerVersions: () => Effect.Effect<ImporterVersions, CatalogAssemblyFailure>;
+  /**
+   * Discard the memoized assembly so the **next** read re-assembles — the same
+   * single read and hook replay as the first, over the workspace as it stands
+   * then.
+   *
+   * @remarks
+   * The explicit memoization boundary for a tool that **mutates the workspace
+   * mid-run** — installs, bumps a config dependency, regenerates the lockfile.
+   * Release-age gating wants the before-state, a post-install peer check the
+   * after-state, and one infinite memo cannot serve both without this call in
+   * between; without it, `peerDependencyRules` keeps answering from the
+   * pre-mutation hook replay and the checker reports findings the new rules
+   * suppress.
+   *
+   * Unconditional and infallible: the memo is already success-only (a failed
+   * or interrupted assembly retries by itself), so `refresh` exists solely to
+   * discard a *successful* assembly that mutation has made stale. Calling it
+   * before any read is harmless.
+   */
+  readonly refresh: () => Effect.Effect<void>;
 }
 /**
  * Options for the {@link WorkspaceCatalogs} layer.
@@ -2554,6 +2574,11 @@ declare class WorkspaceCatalogs extends WorkspaceCatalogs_base {
    * the importer index from the lockfile's importer blocks — neither is in a
    * `CatalogSet`) and always die unless stubbed.
    *
+   * `refresh` defaults to `Effect.void` honestly: the double holds no memo,
+   * so "drop the memoized assembly" is genuinely a no-op — the stubs answer
+   * fresh on every call already. This mirrors `WorkspaceDiscovery.makeTest`'s
+   * `refresh`.
+   *
    * @example
    * ```ts
    * import { CatalogSet, WorkspaceCatalogs } from "@effected/workspaces";

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@effected/workspaces",
-	"version": "0.16.0",
+	"version": "0.17.0",
 	"private": false,
 	"description": "Monorepo workspace tooling as Effect services — root discovery, package enumeration, the dependency graph, package-manager detection, pnpm catalog resolution, lockfile IO and git-based change detection.",
 	"keywords": [
@@ -49,7 +49,7 @@
 		"@effected/commands": "^0.5.0",
 		"@effected/git": "^0.9.0",
 		"@effected/glob": "^0.4.0",
-		"@effected/lockfiles": "^0.6.1",
+		"@effected/lockfiles": "^0.6.2",
 		"@effected/npm": "^0.11.1",
 		"@effected/package-json": "^0.10.2",
 		"@effected/semver": "^0.5.0",