create-deka-app 0.53.4 → 0.53.6

package/README.md

@@ -41,13 +41,17 @@ two publish together, from the same CI run (`.github/workflows/publish-runtime.y
 the `deka` family), so a given create-deka-app version always produces the
 same project: no registry lookup needed to decide the pin.
 
-The one exception is a create-deka-app release whose exact-matching
-runtime build isn't published yet (or a scaffolder-only release cut via
-`publish.yml`'s `v*` tag path, which has no runtime counterpart at all).
-If installing the exact pin fails, create-deka-app falls back to the
-latest published `@dekaruntime/deka` version, prints a clear warning, and
-never leaves a nonexistent version pinned in the generated
-`package.json`.
+There is one publish path for this whole repo: create-deka-app has no
+standalone release of its own. The version in this repo's own
+`package.json` is a `0.0.0` placeholder — it is never bumped by hand or
+committed as part of a release; the workflow stamps the real version into
+it at publish time, in the working tree only.
+
+The one exception to the lockstep pin is a create-deka-app release whose
+exact-matching runtime build isn't published yet. If installing the exact
+pin fails, create-deka-app falls back to the latest published
+`@dekaruntime/deka` version, prints a clear warning, and never leaves a
+nonexistent version pinned in the generated `package.json`.
 
 ## Platforms
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-deka-app",
-  "version": "0.53.4",
+  "version": "0.53.6",
   "description": "Scaffold a new deka app",
   "bin": {
     "create-deka-app": "./index.js"

package/src/scaffold.js

@@ -199,12 +199,12 @@ export function createApp({
   // given create-deka-app version always produces the same project).
   //
   // The one case this doesn't cover is a create-deka-app release whose
-  // exact-matching runtime build isn't published yet (or never will be --
-  // e.g. a scaffolder-only patch released via publish.yml, see its header
-  // comment). That surfaces as the install below failing, and is handled
-  // as a fallback: re-resolve against the registry and retry once, never
-  // silently leaving a nonexistent version pinned in the final
-  // package.json (the ETARGET bug fixed in 0.0.3).
+  // exact-matching runtime build isn't published yet (there is no
+  // standalone scaffolder-only release path -- one publish path,
+  // .github/workflows/publish-runtime.yml). That surfaces as the install
+  // below failing, and is handled as a fallback: re-resolve against the
+  // registry and retry once, never silently leaving a nonexistent version
+  // pinned in the final package.json (the ETARGET bug fixed in 0.0.3).
   let runtimeVersion = resolveRuntimeVersion({ ownVersion })
 
   const writePackageJson = (version) => {