@dbx-tools/projen 0.6.102 → 0.6.103

package/README.md

@@ -251,14 +251,14 @@ Every repo-wide task lives on the root, and the root's `compile` / `test`
 delegate with `bun run --filter '*'` rather than emitting a step per member - so
 a new package is covered without a re-synth. Work from the root:
 
-| Task              | What it does                                       |
-| ----------------- | -------------------------------------------------- |
-| `bun run build`   | `compile` + `test` + `package` across every member |
-| `bun run compile` | `tsc --build` in each member, in parallel          |
-| `bun run test`    | `eslint` once, then each member's tests            |
-| `bun run sync`    | re-synth (`--watch` to keep synthing)              |
-| `bun run barrels` | regenerate the read-only `index.ts` barrels        |
-| `bun run bump`    | version, tag, and publish                          |
+| Task              | What it does                                          |
+| ----------------- | ----------------------------------------------------- |
+| `bun run build`   | workspace `compile` + `test`; no root package fan-out |
+| `bun run compile` | `tsc --build` in each member, in parallel             |
+| `bun run test`    | `eslint` once, then each member's tests               |
+| `bun run sync`    | re-synth (`--watch` to keep synthing)                 |
+| `bun run barrels` | regenerate the read-only `index.ts` barrels           |
+| `bun run bump`    | version, tag, and publish                             |
 
 `bump` also mirrors a release into local registries when the active clients are
 pointed at loopback services. npm uses `npm config get registry` and publishes
@@ -292,10 +292,14 @@ invokes, so there is no second place to run the same thing:
   and publishes with lifecycle scripts disabled).
 - `watch` - a single-package `tsc --build -w`, for narrowing a long
   edit/compile loop to one package.
-- `build` / `install` / `install:ci` / `default` / `pre-compile` /
-  `post-compile` / `package` - projen's own lifecycle scaffolding, emitted for
-  every member because projen's task model expects them. Nothing in this repo's
-  workflow calls them per member.
+- `build` / `package` - a complete compile/test/pack lifecycle when invoked in
+  one package. Root bump deliberately bypasses these and uses filtered compile
+  plus concurrent `bun publish --ignore-scripts`. The package phase also packs
+  with `--ignore-scripts` because its build already compiled; `prepack` remains
+  available for a standalone publish that did not run `build` first.
+- `install` / `install:ci` / `default` / `pre-compile` / `post-compile` -
+  projen's lifecycle scaffolding, emitted for every member because its task model
+  expects them.
 
 Do NOT run `projen default` (or `bunx projen`) from inside a member. Synth is a
 whole-tree operation driven by the ROOT `.projenrc.ts`, so a member-level run

package/package.json

@@ -26,9 +26,9 @@
   },
   "dependencies": {
     "@clack/prompts": "^1.7.0",
-    "@dbx-tools/core": "0.6.102",
-    "@dbx-tools/path": "0.6.102",
-    "@dbx-tools/shared-core": "0.6.102",
+    "@dbx-tools/core": "0.6.103",
+    "@dbx-tools/path": "0.6.103",
+    "@dbx-tools/shared-core": "0.6.103",
     "commander": "^15.0.0",
     "concurrently": "^10.0.3",
     "constructs": "^10.6.0",
@@ -47,7 +47,7 @@
   },
   "main": "index.ts",
   "license": "Apache-2.0",
-  "version": "0.6.102",
+  "version": "0.6.103",
   "types": "index.ts",
   "type": "module",
   "exports": {

package/src/project-js.ts

@@ -380,14 +380,13 @@ function defaultProjectOptions(
     ...(isRoot ? {} : { npmAccess: javascript.NpmAccess.PUBLIC }),
     buildWorkflow: false,
     release: false,
-    // No `npm pack` step on any project. projen wires `package` into `build`, so
-    // `bunx projen build` would tarball all 36 manifests (root included) into
-    // gitignored `dist/js` on every CI run and never read them: publishing here
-    // is the workspace publish task compiling packages once from the root before
-    // `bun publish --ignore-scripts` packs them (see {@link applyCompiledPublish}),
-    // and `release: false` means no projen Publisher exists to consume the
-    // artifacts either.
-    package: false,
+    // The root build validates the whole workspace and must not also pack every
+    // member into unused `dist/js` tarballs. Child projects keep projen's package
+    // task so `bun run build` in ONE package remains a complete compile/test/pack
+    // operation. The root bump does not invoke child builds: its publish driver
+    // compiles once with filtered root tasks and packs via
+    // `bun publish --ignore-scripts` (see {@link applyCompiledPublish}).
+    ...(isRoot ? { package: false } : {}),
     jest: false,
     github: false,
     npmignoreEnabled: false,
@@ -970,6 +969,15 @@ function initProject(
 
   if (project.parent) {
     project.package.file.readonly = true;
+    // `build` already compiles before its `package` phase. Keep the package's
+    // `prepack` for standalone `bun publish`, but suppress lifecycle scripts in
+    // this generated pack step so a direct child build does not compile twice.
+    const packageStep = project.packageTask.steps.find(
+      (step) => step.execArgs?.[0] === "npm" && step.execArgs[1] === "pack",
+    );
+    if (packageStep?.execArgs && !packageStep.execArgs.includes("--ignore-scripts")) {
+      packageStep.execArgs.push("--ignore-scripts");
+    }
     // Stamp `repository` (with this package's `directory` subpath) so a published
     // package passes npm provenance validation.
     applyRepository(project, options.repository);

package/tasks/bump.ts

@@ -265,7 +265,7 @@ program
             "-m",
             "🌸 Shipped with Kanna — https://kanna.sh",
             "-m",
-            "Co-Authored-By: Kanna <noreply@kanna.sh>\nKanna-Agent: codex/databricks-gpt-5-6-sol",
+            "Co-Authored-By: Kanna <noreply@kanna.sh>\nKanna-Agent: codex/gpt",
           ]);
         } else logger.info("nothing to commit");
       }