@effected/workspaces 0.9.0 → 0.9.1

package/PackageManagerName.js

@@ -292,6 +292,11 @@ var PackageManagerDetector = class PackageManagerDetector extends Context.Servic
 	* reads as a legitimate "no manager here" answer, so a consumer would branch
 	* on it and proceed, never learning that the test simply forgot to stub.
 	*
+	* The defect is also not absorbed by `Effect.catch` or any typed-error
+	* handler — deliberately, so code under test with a best-effort `catch`
+	* around detection cannot make the mandatory stub look optional; the
+	* unstubbed call still fails the test.
+	*
 	* @param overrides - Members to supply; anything omitted dies on use.
 	*
 	* @example

package/Publishability.js

@@ -137,8 +137,15 @@ var PublishabilityDetector = class extends Context.Service()("@effected/workspac
 	* silence — `Layer.mergeAll(myDetector, Workspaces.layer())` resolved to the
 	* default, because `mergeAll` is last-wins. For a service that decides
 	* whether a package publishes and to which registry, that silent revert was
-	* the worst available failure. The requirement now sits in `R`, so the
-	* choice is made once, explicitly, and unmade wiring does not compile.
+	* the worst available failure.
+	*
+	* The composites do not *require* a detector either — nothing inside them
+	* asks a publishability question, so their `R` stays `FileSystem | Path`.
+	* The requirement instead surfaces in the `R` of each operation that asks
+	* (`VersioningStrategy.detect`, e.g.): a program that asks and never wires
+	* a detector fails to compile where that operation's `R` must close — which
+	* can be far from the layer-wiring site — and a program that never asks
+	* never supplies a publish policy at all.
 	*/
 	static layerNpm = Layer.succeed(this, this.npm);
 	/**

package/README.md

@@ -232,7 +232,9 @@ A name miss in the derived `getPackage` fails with the service's own typed `Pack
 - `WorkspaceCatalogs` — pnpm catalog assembly and `catalog:` resolution, on pnpm's own catalog packages; `releaseAgeGate()` assembles the effective `@effected/npm` `ReleaseAgeGate` from inline `pnpm-workspace.yaml` release-age keys and replayed hook contributions, strictest-wins, in the same pass as the catalogs.
 - `LockfileReader` — locate and parse the workspace's lockfile through `@effected/lockfiles`.
 - `ChangeDetector` — git-range change detection over `@effected/git`'s `Git` service; swap the layer to mock it with no repository.
-- `PublishabilityDetector` — whether a package publishes and to where, as a `PublishTarget` (registry, directory, access, provenance). The default layer implements npm's semantics; swap the layer if yours differ.
+- `PublishabilityDetector` — whether a package publishes and to where, as a `PublishTarget` (registry, directory, access, provenance). No composite provides one: pick `PublishabilityDetector.layerNpm` (standard npm semantics) or `.layerNone` (nothing publishes) and provide it explicitly.
+- `ReleaseTag` / `TrackingTag` — release-tag formatting (`ReleaseTag.single` / `.scoped`, strict SemVer by default with no `v` prefix) and the floating major/minor alias derivation GitHub Actions-style consumers expect (`v1`, `v1.2`), plus `classifyTag` to tell a release tag from a tracking alias.
+- `VersioningStrategy` — classify a workspace as `single`, `fixed-group` or `independent` from package names and fixed groups, or detect it live against `PublishabilityDetector`, and produce the release tags for a batch with `tagsFor`.
 - `findWorkspaceRootSync` / `getWorkspacePackagesSync` — the synchronous escape hatch for config-time callers that cannot await, over file and path operations you supply.
 - `@effected/workspaces/node-sync` — a second entry point holding the Node bindings for those operations (`nodeFileSystem`, `nodePath` and the `nodeSyncOps` bag), kept off the main entry so `node:*` never reaches a consumer that supplies its own.
 

package/WorkspaceDiscovery.js

@@ -326,7 +326,10 @@ var WorkspaceDiscovery = class WorkspaceDiscovery extends Context.Service()("@ef
 	*   (a fabricated root path would leak into consumer path logic), so an
 	*   unstubbed `info()` call is a test-wiring mistake and fails loudly as a
 	*   defect rather than succeeding with a lie or failing with a dishonest
-	*   typed error.
+	*   typed error. A defect is not absorbed by `Effect.catch` or any
+	*   typed-error handler — deliberately, so code under test with a
+	*   best-effort `catch` cannot make the mandatory stub look optional; the
+	*   unstubbed call still fails the test.
 	*
 	* @example
 	* ```ts

package/WorkspaceSnapshots.js

@@ -175,7 +175,7 @@ var WorkspaceSnapshots = class WorkspaceSnapshots extends Context.Service()("@ef
 		return {
 			at: Effect.fn("WorkspaceSnapshots.at")(function* (ref) {
 				const root = yield* Effect.suspend(() => roots.find(options?.cwd ?? process.cwd()));
-				const key = `${root}${ref}`;
+				const key = `${root}\0${ref}`;
 				let memo = atCaches.get(key);
 				if (memo === void 0) {
 					const [resolveOnce, invalidate] = yield* Effect.cachedInvalidateWithTTL(computeAt(root, ref), Duration.infinity);
@@ -233,6 +233,13 @@ var WorkspaceSnapshots = class WorkspaceSnapshots extends Context.Service()("@ef
 	* test-wiring mistake fails loudly as a defect rather than succeeding with a
 	* lie.
 	*
+	* **A defect is not absorbed by `Effect.catch` or any typed-error handler**,
+	* and that is the point: code under test with a best-effort `catch` around
+	* its snapshot reads cannot make a mandatory stub look optional — the
+	* unstubbed call still fails the test instead of quietly taking the catch
+	* branch. Only defect-level combinators (`Effect.catchDefect`,
+	* `Effect.exit`) would see it.
+	*
 	* @example
 	* ```ts
 	* import { CatalogSet, WorkspaceSnapshots, WorkspaceStateSnapshot } from "@effected/workspaces";

package/Workspaces.js

@@ -42,11 +42,12 @@ const localExecLayer = (options) => Layer.effect(LocalExec, Effect.gen(function*
 			cause
 		})));
 		if (Option.isNone(detected)) return Option.none();
-		const { prefix, dlxPrefix } = LocalExec.prefixes(detected.value.name);
+		const { prefix, dlxPrefix, scriptPrefix } = LocalExec.prefixes(detected.value.name);
 		return Option.some(ExecContext.make({
 			label: detected.value.name,
 			prefix,
 			dlxPrefix,
+			scriptPrefix,
 			directory: root.value
 		}));
 	}) };
@@ -60,13 +61,23 @@ var Workspaces = class {
 	constructor() {}
 	/**
 	* Every service that needs only a filesystem: root, package-manager
-	* detection, discovery, lockfile reading, catalogs and publishability.
+	* detection, discovery, lockfile reading and catalogs.
 	*
 	* @remarks
 	* Requires core `FileSystem` and `Path`, which the consumer provides at the
 	* edge (`@effect/platform-node`, `@effect/platform-bun`, or a test's
 	* `FileSystem.layerNoop`).
 	*
+	* **`PublishabilityDetector` is neither provided nor required here.** The
+	* composite used to bake in npm semantics, which a naively-ordered override
+	* silently lost to; now it supplies no default, and — because nothing inside
+	* the composite asks a publishability question — it does not require one in
+	* `R` either. The requirement surfaces in the `R` of each operation that
+	* asks (`VersioningStrategy.detect`, e.g.), so a program that asks and never
+	* wires a detector fails to compile at that operation, and a program that
+	* never asks never supplies a publish policy. Wire one explicitly where
+	* needed: `Layer.mergeAll(Workspaces.layer(), PublishabilityDetector.layerNpm)`.
+	*
 	* **Bind the result to a `const`.** This is a parameterized factory and
 	* layers memoize by reference, so calling it twice builds everything twice.
 	*
@@ -122,7 +133,8 @@ var Workspaces = class {
 	* it. So `commands` declares the narrow contract and we ship the layer.
 	*
 	* **The argv knowledge is not duplicated.** `LocalExec.prefixes(name)` is
-	* the one home of the four managers' `exec`/`dlx` prefixes; this layer
+	* the one home of the four managers' `exec`/`dlx`/script-runner prefixes;
+	* this layer
 	* detects *which* manager owns the directory and asks `commands` what that
 	* manager's argv looks like. Neither package reimplements the other's
 	* half.

package/index.d.ts

@@ -607,7 +607,10 @@ declare class WorkspaceDiscovery extends WorkspaceDiscovery_base {
    *   (a fabricated root path would leak into consumer path logic), so an
    *   unstubbed `info()` call is a test-wiring mistake and fails loudly as a
    *   defect rather than succeeding with a lie or failing with a dishonest
-   *   typed error.
+   *   typed error. A defect is not absorbed by `Effect.catch` or any
+   *   typed-error handler — deliberately, so code under test with a
+   *   best-effort `catch` cannot make the mandatory stub look optional; the
+   *   unstubbed call still fails the test.
    *
    * @example
    * ```ts
@@ -1126,6 +1129,11 @@ declare class PackageManagerDetector extends PackageManagerDetector_base {
    * reads as a legitimate "no manager here" answer, so a consumer would branch
    * on it and proceed, never learning that the test simply forgot to stub.
    *
+   * The defect is also not absorbed by `Effect.catch` or any typed-error
+   * handler — deliberately, so code under test with a best-effort `catch`
+   * around detection cannot make the mandatory stub look optional; the
+   * unstubbed call still fails the test.
+   *
    * @param overrides - Members to supply; anything omitted dies on use.
    *
    * @example
@@ -1474,8 +1482,15 @@ declare class PublishabilityDetector extends PublishabilityDetector_base {
    * silence — `Layer.mergeAll(myDetector, Workspaces.layer())` resolved to the
    * default, because `mergeAll` is last-wins. For a service that decides
    * whether a package publishes and to which registry, that silent revert was
-   * the worst available failure. The requirement now sits in `R`, so the
-   * choice is made once, explicitly, and unmade wiring does not compile.
+   * the worst available failure.
+   *
+   * The composites do not *require* a detector either — nothing inside them
+   * asks a publishability question, so their `R` stays `FileSystem | Path`.
+   * The requirement instead surfaces in the `R` of each operation that asks
+   * (`VersioningStrategy.detect`, e.g.): a program that asks and never wires
+   * a detector fails to compile where that operation's `R` must close — which
+   * can be far from the layer-wiring site — and a program that never asks
+   * never supplies a publish policy at all.
    */
   static readonly layerNpm: Layer.Layer<PublishabilityDetector>;
   /**
@@ -2427,6 +2442,13 @@ declare class WorkspaceSnapshots extends WorkspaceSnapshots_base {
    * test-wiring mistake fails loudly as a defect rather than succeeding with a
    * lie.
    *
+   * **A defect is not absorbed by `Effect.catch` or any typed-error handler**,
+   * and that is the point: code under test with a best-effort `catch` around
+   * its snapshot reads cannot make a mandatory stub look optional — the
+   * unstubbed call still fails the test instead of quietly taking the catch
+   * branch. Only defect-level combinators (`Effect.catchDefect`,
+   * `Effect.exit`) would see it.
+   *
    * @example
    * ```ts
    * import { CatalogSet, WorkspaceSnapshots, WorkspaceStateSnapshot } from "@effected/workspaces";
@@ -2502,13 +2524,23 @@ declare class Workspaces {
   private constructor();
   /**
    * Every service that needs only a filesystem: root, package-manager
-   * detection, discovery, lockfile reading, catalogs and publishability.
+   * detection, discovery, lockfile reading and catalogs.
    *
    * @remarks
    * Requires core `FileSystem` and `Path`, which the consumer provides at the
    * edge (`@effect/platform-node`, `@effect/platform-bun`, or a test's
    * `FileSystem.layerNoop`).
    *
+   * **`PublishabilityDetector` is neither provided nor required here.** The
+   * composite used to bake in npm semantics, which a naively-ordered override
+   * silently lost to; now it supplies no default, and — because nothing inside
+   * the composite asks a publishability question — it does not require one in
+   * `R` either. The requirement surfaces in the `R` of each operation that
+   * asks (`VersioningStrategy.detect`, e.g.), so a program that asks and never
+   * wires a detector fails to compile at that operation, and a program that
+   * never asks never supplies a publish policy. Wire one explicitly where
+   * needed: `Layer.mergeAll(Workspaces.layer(), PublishabilityDetector.layerNpm)`.
+   *
    * **Bind the result to a `const`.** This is a parameterized factory and
    * layers memoize by reference, so calling it twice builds everything twice.
    *
@@ -2564,7 +2596,8 @@ declare class Workspaces {
    * it. So `commands` declares the narrow contract and we ship the layer.
    *
    * **The argv knowledge is not duplicated.** `LocalExec.prefixes(name)` is
-   * the one home of the four managers' `exec`/`dlx` prefixes; this layer
+   * the one home of the four managers' `exec`/`dlx`/script-runner prefixes;
+   * this layer
    * detects *which* manager owns the directory and asks `commands` what that
    * manager's argv looks like. Neither package reimplements the other's
    * half.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@effected/workspaces",
-	"version": "0.9.0",
+	"version": "0.9.1",
 	"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": [
@@ -46,12 +46,12 @@
 		"./package.json": "./package.json"
 	},
 	"dependencies": {
-		"@effected/commands": "~0.1.0",
+		"@effected/commands": "~0.2.0",
 		"@effected/git": "~0.5.1",
 		"@effected/glob": "~0.2.1",
-		"@effected/lockfiles": "~0.2.1",
-		"@effected/npm": "~0.5.0",
-		"@effected/package-json": "~0.6.0",
+		"@effected/lockfiles": "~0.2.2",
+		"@effected/npm": "~0.6.0",
+		"@effected/package-json": "~0.6.1",
 		"@effected/semver": "~0.2.1",
 		"@effected/walker": "~0.3.3",
 		"@effected/yaml": "~0.6.0",