@sous-io/sous 0.2.0 → 0.2.1

package/docs/markdown/commands.md

@@ -246,7 +246,7 @@ These three run inside a recipe repository and take none of the config-locating
 `sous repo release` plans first, asks once, and then bumps, regenerates the index, commits and
 tags in one run. `--namespace` and `--recipe` are repeatable and narrow the run; `--check` reads
 only and cannot be combined with `--bump`, `--tag` or `--push`; `--ci` is the merge preset and
-implies `--no-bump`. See [Authoring a repository](repositories-authoring.md).
+implies both `--no-bump` and `--yes`, so it prints the plan and carries it out without asking. See [Authoring a repository](repositories-authoring.md).
 
 ## Variables
 

package/docs/markdown/repositories-authoring.md

@@ -287,7 +287,7 @@ Three facts about each recipe decide everything, and nothing else does:
 | `sous repo release --tag` | Cut the tags even on a branch other than the default one |
 | `sous repo release --push` | Push the commit, and the tags this run created, to `origin` |
 | `sous repo release --check` | Read only: validate, and fail when the committed index is out of date |
-| `sous repo release --ci` | The merge preset: never bump, never ask, fail on anything unbumped |
+| `sous repo release --ci` | The merge preset: never bump, accept the plan, never ask, fail on anything unbumped |
 
 ### The branch rule
 
@@ -346,11 +346,12 @@ repository:
 - On a **pull request**, `sous repo release --check`. It only reads, so it is safe on an
   untrusted branch, and it fails the pull request when a manifest is wrong or the committed index
   (including the dependencies it records) is stale.
-- On a **push to the default branch**, `sous repo release --ci --push`. `--ci` raises no versions
-  and asks no questions: the version bump belongs in the change being merged, so a recipe that
-  changed without one fails here rather than being given a version nobody reviewed. Both
-  checkouts use `fetch-depth: 0`, so existing tags are visible and a published version is never
-  cut a second time.
+- On a **push to the default branch**, `sous repo release --ci --push --yes`. `--ci` raises no
+  versions, accepts the plan it prints, and asks no questions: the version bump belongs in the
+  change being merged, so a recipe that changed without one fails here rather than being given a
+  version nobody reviewed. `--ci` implies `--yes`; the workflow passes it as well so the same
+  file works with an older sous. Both checkouts use `fetch-depth: 0`, so existing tags are
+  visible and a published version is never cut a second time.
 
 ## Contribute to someone else's repository
 

package/docs/markdown/repositories-file-formats.md

@@ -1039,7 +1039,7 @@ that tag.
 | `sous repo release --tag` | Cut the tags even on a branch other than the default one. |
 | `sous repo release --push` | Push the commit, and the tags this run created, to `origin`. |
 | `sous repo release --check` | Read only: validate, and fail when the committed index is out of date. This is what a pull request runs. |
-| `sous repo release --ci` | The merge preset: never bump, never ask, fail on anything unbumped. |
+| `sous repo release --ci` | The merge preset: never bump, accept the plan, never ask, fail on anything unbumped. |
 
 Tags are cut dependency-first, and each version's resolved dependencies are written into the
 index. On a branch other than the default one a release bumps and commits but cuts no tags,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sous-io/sous",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Compiles AI coding agent configuration (CLAUDE.md, skills, memories) from LiquidJS templates",
   "type": "module",
   "license": "Apache-2.0",

package/recipes/core/sous-skills/sous.recipe.yaml

@@ -11,7 +11,7 @@ formatVersion: 1
 
 namespace: core
 name: sous-skills
-version: 0.2.0
+version: 0.2.1
 
 description: >-
   The skills that teach an agent what sous is and how it works: which files sous

package/src/commands/repo/release.ts

@@ -77,7 +77,8 @@ const RELEASE_REMOTE = "origin";
  *
  * Two presets sit on top of it. `--check` is read-only and is what a pull
  * request runs; `--ci` is the non-interactive form a merge runs, which bumps
- * nothing because the version was raised in the change being merged.
+ * nothing because the version was raised in the change being merged, and which
+ * accepts the plan it prints because there is nobody there to accept it.
  */
 export default class RepoRelease extends Command {
   static description =
@@ -106,7 +107,8 @@ export default class RepoRelease extends Command {
     }),
     ci: Flags.boolean({
       description:
-        "Run the way a merge does: never bump, never ask, and fail on anything unbumped",
+        "Run the way a merge does: never bump, accept the plan, never ask, and fail on " +
+        "anything unbumped",
       default: false,
     }),
     namespace: Flags.string({
@@ -156,10 +158,14 @@ export default class RepoRelease extends Command {
     const { flags } = await this.parse(RepoRelease);
     const dryRun = flags["dry-run"];
     const ci = flags.ci;
-    // The CI preset is exactly two settings: never raise a version, and never
-    // ask. It deliberately does NOT imply --push; the workflow passes that
-    // itself, so what gets pushed is visible in the workflow file.
+    // The CI preset is exactly three settings: never raise a version, accept
+    // the plan it prints, and never ask. Accepting the plan is part of the
+    // preset because there is nobody to ask: a run that only refused to ask
+    // would fail on the very confirmation the preset exists to answer. It
+    // deliberately does NOT imply --push; the workflow passes that itself, so
+    // what gets pushed is visible in the workflow file.
     const noBump = flags["no-bump"] || ci;
+    const accepted = flags.yes || ci;
     const interactive = ci ? false : isInteractive();
 
     assertFlagsAgree({ ...flags, noBump });
@@ -222,7 +228,7 @@ export default class RepoRelease extends Command {
 
     // --- Confirm ----------------------------------------------------------
 
-    if (!flags.yes) {
+    if (!accepted) {
       if (!interactive) {
         throw nonInteractiveError({
           prompt: "whether to publish the versions listed above",
@@ -232,8 +238,8 @@ export default class RepoRelease extends Command {
         });
       }
       blankLine();
-      const accepted = await askYesNo("Publish these versions?");
-      if (!accepted) {
+      const answer = await askYesNo("Publish these versions?");
+      if (!answer) {
         blankLine();
         log("  Nothing was written.");
         footer();

package/src/lib/repos/scaffold/templates.ts

@@ -332,12 +332,14 @@ export function buildReleaseWorkflow(): string {
 #   declare. It only reads; it never writes, commits or tags. That makes it the
 #   right thing to run on a pull request.
 #
-#   'sous repo release --ci --push' does the same validation and then publishes.
-#   '--ci' raises no versions and asks no questions: the version bump belongs in
-#   the change being merged, so a recipe that changed without one fails here
-#   rather than being given a version nobody reviewed. It cuts an annotated tag
-#   for every version that does not have one yet, dependency-first, and '--push'
-#   pushes the commit and those tags.
+#   'sous repo release --ci --push --yes' does the same validation and then
+#   publishes. '--ci' raises no versions, accepts the plan it prints, and asks
+#   no questions: the version bump belongs in the change being merged, so a
+#   recipe that changed without one fails here rather than being given a version
+#   nobody reviewed. It cuts an annotated tag for every version that does not
+#   have one yet, dependency-first, and '--push' pushes the commit and those
+#   tags. '--ci' implies '--yes'; passing it as well keeps this workflow working
+#   with a sous old enough that it did not.
 
 name: sous release
 
@@ -385,7 +387,7 @@ jobs:
           git config user.name "github-actions[bot]"
           git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
       - name: Publish every new version
-        run: npx --yes @sous-io/sous repo release --ci --push
+        run: npx --yes @sous-io/sous repo release --ci --push --yes
 `;
 }