@akanjs/devkit 3.2.0-rc.6 → 3.2.0-rc.7

package/CHANGELOG.md

@@ -131,6 +131,7 @@
     - The dev builder draws the graph on request through a new `build-graph` builder RPC, and keeps it until the next save.
     - It sits behind the same gate as the other `/_akan` devtools routes, and `akan tunnel` / `akan start --share` refuse it.
 
+- 2d3b958: `ApiReportPolicy.check` counts a changeset that a branch adds in place of a similar one it deletes. git's rename detection paired the two, so the added changeset was not listed and its `minor` bump did not satisfy the check.
 - 465ccb9: `@akanjs/devkit/apiReport/apiReport` renders a package's public API, one report per entry point, from its declaration emit. The akanjs repository now commits that report for `akanjs` and checks it in CI: a removed export or a changed declaration needs a `minor` changeset that says how to upgrade.
 - 0504209: `akan build <app> --env <env>` builds for an environment other than the workspace `.env`'s, the way the desktop and mobile builds already do. Before, the shell's `AKAN_PUBLIC_ENV` lost to the `.env`, so a new workspace could only build `local` without editing it. The local-build notice, the image guard and the README now say what a `local` build changes in a built server: no endpoint rate limits, and local defaults for Redis and the database mode. They no longer say the dev routes are served, which a built server never does.
 - bf872ce: A variable the shell sets now outranks the workspace `.env` when `akan` builds or runs an app, as dotenv and Bun's own `.env` loading do: `AKAN_PUBLIC_ENV=main akan build <app>` builds `main` where the `.env` says `local`. The order is `--env` (for `AKAN_PUBLIC_ENV`), then the process environment (the shell, and the `.env.local` and `.env.<NODE_ENV>` Bun loads into it), then the `.env`, then the defaults; an empty export counts as unset. The bundles, the bundled server env, `akan.env.json` and the Dockerfile still take one set of values. Where an exported value outranks the `.env`, `akan build` now warns with both values instead of the old warning that listed the values it ignored, and the server-env message, the `--env` help, the local-build notice, the README and the CLI reference state the new order.
@@ -392,6 +393,7 @@
 
 - d2b2291: A failed workflow no longer reports success to its caller. `akan workflow plan` exits 1 when the plan has an error, `akan workflow apply` when the apply or its `--dry-run` fails, and `akan workflow validate` when its status is `failed` (which includes `passed-with-baseline-blockers`); all three exited 0 before. A dry run of a plan with an error, such as `add-field --type Number`, reports `failed` and lists no changed or generated files, where it used to list the plan's edits under "Automatically Modified". Over MCP, `plan_workflow` names `apply_workflow` in `next` and `approval.canApplyWith` only for a plan without an error, and `apply_workflow` names `run_validation` only when the apply did not fail; a refused plan also drops its "apply this plan" and "validate the apply report" recommendations. The workflows that write into an existing module (`add-field`, `add-enum-field`, `add-mutation`, `add-slice`, `create-ui`, `rename-key`) now refuse a service module, or any folder without its `<module>.constant.ts`, at plan time and again at apply. The `workflow-module-not-database` error lists the target's database modules and points at `create-module`, and for a field at `create-scalar`. Before, `add-field` on a service module passed its plan and dry run and failed only at apply, and `create-ui` wrote a misnamed `_<service>.View.tsx` into it. The `workflow-module-missing` error now lists only database modules too, says a name that matches a service module (with or without its `_`) is one instead of asking "Did you mean \_<service>?", and points at another app or library only when it holds a database module of that name.
 - adcdf3b: `akan workflow plan` and the `plan_workflow` MCP tool refuse a module the target app or library lacks, for every workflow that writes into an existing module (`add-field`, `add-enum-field`, `add-mutation`, `add-slice`, `create-ui`, `rename-key`). The `workflow-module-missing` error names the module, lists the modules the target has, and points at the module whose name differs only in case or by a leading `_`, at a scalar of that name, or at the app or library that holds it; only when none exists does it point at `create-module`. Before, the plan passed and its dry run reported `passed`. `add-mutation` used to plan a missing module with a warning so that a `create-module` plan could precede it; it now refuses too, so plan it after applying `create-module`. Every workflow now refuses an unknown `app` at plan time, listing the workspace's apps and libraries. `apply` and `--dry-run` check the target again before anything else, so a plan written earlier for a module that is gone fails instead of passing. `plan_workflow` now inspects the MCP server's workspace rather than the process directory.
+- Updated dependencies [bd198af]
 - Updated dependencies [bc792ab]
 - Updated dependencies [31f7039]
 - Updated dependencies [61fbd7d]
@@ -440,6 +442,7 @@
 - Updated dependencies [5cd1fc3]
 - Updated dependencies [f47cc82]
 - Updated dependencies [7f0de74]
+- Updated dependencies [c0b84d0]
 - Updated dependencies [1f93507]
 - Updated dependencies [5d3cb3e]
 - Updated dependencies [9a9e1fa]

package/apiReport/apiReport.test.ts

@@ -476,6 +476,20 @@ describe("ApiReportPolicy", () => {
     expect((await policy.check("main"))?.bumped).toBe(false);
   });
 
+  test("counts a changeset added in place of a similar one from the base", async () => {
+    const note = "Every app's client declaration names the Err type instead of spelling out its class.\n".repeat(4);
+    const { root, policy } = await makeRepo(
+      { "demo.api.md": reportOf("export declare const a: number;", "export declare const b: number;") },
+      { ".changeset/older.md": `---\n"akanjs": patch\n---\n\n${note}` },
+    );
+    await writeText(path.join(root, "api-report/demo/demo.api.md"), reportOf("export declare const a: number;"));
+    await rm(path.join(root, ".changeset/older.md"));
+    await writeText(path.join(root, ".changeset/newer.md"), `---\n"akanjs": minor\n---\n\n${note}`);
+    git(root, "add", "-A");
+    git(root, "commit", "-q", "-m", "drop b");
+    expect((await policy.check("main"))?.bumped).toBe(true);
+  });
+
   test("answers null for a ref that names no commit", async () => {
     const { policy } = await makeRepo({});
     expect(await policy.check("origin/missing")).toBeNull();

package/apiReport/apiReportPolicy.ts

@@ -43,9 +43,10 @@ export class ApiReportPolicy {
     const breaks = ApiReportDiff.breaks(before, await this.readReports());
     if (!breaks.length) return { breaks, bumped: false };
     const added = [
-      ...((await this.#git(["diff", "--name-only", "--diff-filter=A", mergeBase, "--", ".changeset"])) ?? "").split(
-        "\n",
-      ),
+      ...(
+        (await this.#git(["diff", "--name-only", "--no-renames", "--diff-filter=A", mergeBase, "--", ".changeset"])) ??
+        ""
+      ).split("\n"),
       ...((await this.#git(["ls-files", "--others", "--exclude-standard", "--", ".changeset"])) ?? "").split("\n"),
     ].filter((file) => file.endsWith(".md") && !file.endsWith("README.md"));
     const bumps = await Promise.all(

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@akanjs/devkit",
-  "version": "3.2.0-rc.6",
+  "version": "3.2.0-rc.7",
   "sourceType": "module",
   "type": "module",
   "publishConfig": {
@@ -41,7 +41,7 @@
     "./*": "./*.ts"
   },
   "dependencies": {
-    "@akanjs/language": "3.2.0-rc.6",
+    "@akanjs/language": "3.2.0-rc.7",
     "@earendil-works/pi-agent-core": "1.3.0",
     "@earendil-works/pi-ai": "1.3.0",
     "@earendil-works/pi-codemode": "1.3.0",
@@ -50,7 +50,7 @@
     "@earendil-works/pi-tui": "1.3.0",
     "@inquirer/prompts": "^8.7.3",
     "@tailwindcss/node": "^4.3.3",
-    "akanjs": "3.2.0-rc.6",
+    "akanjs": "3.2.0-rc.7",
     "chalk": "^6.0.1",
     "commander": "^15.0.0",
     "dayjs": "^1.11.23",