uniweb 1.21.7 → 1.21.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "1.21.7",
+  "version": "1.21.8",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -41,15 +41,15 @@
     "js-yaml": "^4.3.2",
     "prompts": "^2.4.2",
     "tar": "^7.5.21",
-    "@uniweb/core": "~1.4.9",
     "@uniweb/content-writer": "~1.3.1",
-    "@uniweb/schemas": "~1.6.5",
-    "@uniweb/semantic-parser": "~1.13.0"
+    "@uniweb/core": "~1.4.9",
+    "@uniweb/semantic-parser": "~1.13.0",
+    "@uniweb/schemas": "~1.6.5"
   },
   "peerDependencies": {
-    "@uniweb/build": "~1.10.6",
-    "@uniweb/semantic-parser": "~1.13.0",
-    "@uniweb/content-reader": "~1.5.7"
+    "@uniweb/build": "~1.10.7",
+    "@uniweb/content-reader": "~1.5.7",
+    "@uniweb/semantic-parser": "~1.13.0"
   },
   "peerDependenciesMeta": {
     "@uniweb/build": {

package/partials/agents.md

@@ -2862,7 +2862,7 @@ uniweb <command> --help           # Per-command flags — no side effects. Prefe
 | Any static host at all | `uniweb export` | full control; no Uniweb account needed |
 | Uniweb Cloud | `uniweb publish` | teams with non-technical content authors, or client work |
 
-`uniweb deploy` never assumes a host: with nothing configured it opens a picker listing only destinations it can act on, and records the choice in `deploy.yml` so later runs go straight there. On Cloudflare Pages / Netlify / Vercel, `add ci` also adds per-PR previews that comment the URL. GitHub runs workflows only from the top of the repository: in a project that is a folder of a larger repository, the project's own `.github/` never runs, and `uniweb status` says so — as it says when a target in `deploy.yml` was never deployed from this copy. Adapters: `github-pages`, `cloudflare-pages`, `netlify`, `vercel`, plus `s3-cloudfront` for `deploy`. That record is `deploy.yml`, beside `site.yml` — **the CLI writes it, you don't create it**: the first successful deploy scaffolds the whole file, and later deploys rewrite only its `deploys:` block. Edit `targets:` when you want to change where a site ships. Host credentials come from the environment, never from that committed file.
+`uniweb deploy` never assumes a host: with nothing configured it opens a picker listing only destinations it can act on, and records the choice in `deploy.yml` so later runs go straight there. On Cloudflare Pages / Netlify / Vercel, `add ci` also adds per-PR previews that comment the URL. GitHub runs workflows only from the top of the repository: in a project that is a folder of a larger repository, the project's own `.github/` never runs — `uniweb status` says so, and `uniweb add ci` refuses to write one there — as it says when a target in `deploy.yml` was never deployed from this copy. Adapters: `github-pages`, `cloudflare-pages`, `netlify`, `vercel`, plus `s3-cloudfront` for `deploy`. That record is `deploy.yml`, beside `site.yml` — **the CLI writes it, you don't create it**: the first successful deploy scaffolds the whole file, and later deploys rewrite only its `deploys:` block. Edit `targets:` when you want to change where a site ships. Host credentials come from the environment, never from that committed file.
 
 Foundations have their own free path too: `uniweb add ci --target foundation` publishes to permanent versioned URLs on GitHub Pages.
 

package/src/commands/add.js

@@ -44,6 +44,7 @@ import {
   resolveUniqueName
 } from '../utils/names.js'
 import { findWorkspaceRoot } from '../utils/workspace.js'
+import { repoOf } from '../utils/sync-point.js'
 import {
   normalizeFoundationName,
   ensureFoundationName,
@@ -1479,6 +1480,20 @@ export default function ${name}({ content, params }) {
  * and can plug in later.
  */
 async function addCi(rootDir, opts, pm = 'pnpm') {
+  // ⛔ A PROJECT THAT IS A FOLDER OF A LARGER REPOSITORY gets no workflow: GitHub runs workflows
+  // only from a repository's top, and this writes into the project's own `.github/`, where it
+  // would never run. Refused rather than written, for now [Diego, 2026-10-26: "refuse for now"] —
+  // measured on a repository of client projects, one of which carried a GitHub Pages workflow
+  // from its old repository that had not run since it moved.
+  const repo = repoOf(rootDir)
+  if (repo?.prefix) {
+    error(`Not added: this project is the folder ${repo.path} of the repository at ${repo.top}.`)
+    log(`  GitHub runs workflows only from the top of a repository (${relative(rootDir, join(repo.top, '.github', 'workflows'))}/),`)
+    log(`  so one written in this project's own .github/ would never run.`)
+    log(`  Deploy from a repository of its own, or by hand from here: uniweb deploy --host=<adapter>.`)
+    process.exit(1)
+  }
+
   // Lazy-load the host registry so the CLI doesn't pay this import on
   // every add invocation.
   let getAdapter, listAdapters

package/src/framework-index.json

@@ -1,12 +1,12 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-10-26T22:50:14.357Z",
+  "generatedAt": "2026-10-26T23:21:20.295Z",
   "packages": {
     "@uniweb/api": {
       "version": "1.6.4"
     },
     "@uniweb/build": {
-      "version": "1.10.6"
+      "version": "1.10.7"
     },
     "@uniweb/content-reader": {
       "version": "1.5.7"
@@ -24,7 +24,7 @@
       "version": "1.0.6"
     },
     "@uniweb/kit": {
-      "version": "1.6.6"
+      "version": "1.6.7"
     },
     "@uniweb/loom": {
       "version": "1.1.2"