@jals1212/ci-local-pi 0.5.0 → 0.5.1

package/CHANGELOG.md

@@ -6,6 +6,14 @@ add or change behaviour and a patch version fixes.
 
 ## Unreleased
 
+## 0.5.1
+
+### Fixed
+
+- The skill says runs may go several at once (`CI_LOCAL_MAX_RUNS`, or
+  `maxRuns` in `~/.ci-local/config.json`, from ci-local 0.10.0), and names the
+  README's queue section by its new title.
+
 ## 0.5.0
 
 ### Added

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jals1212/ci-local-pi",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "description": "Pi extension and skill for @jals1212/ci-local: the state of this repository's ci-local run in Pi's status line, cards and a read-only tool for the agent.",
   "license": "MIT",
   "author": "jals1212",

package/skills/ci-local/SKILL.md

@@ -17,7 +17,7 @@ Use when running, waiting on, reading, or configuring `ci-local` (`npx ci-local`
 - Start a run with the `ci_local_run` tool when present: it returns once the run is queued or started, and its end card reaches you when it ends. Without it, launch in the background (`bash_background` or equivalent) and wait for its exit notice. Never poll, never `sleep`.
 - Unwatched runs are quiet: milestones and the summary on stdout, each step's output in its own log. From 0.5.0 that is the default without a terminal; before 0.5.0, add `--quiet`. Never add `--live` to a background run.
 - Do not touch the checkout while a run is in flight (no edits, no branch switch): the steps read it.
-- Never start a second run to "check" the first. Runs queue machine-wide by themselves (one Docker user at a time); a waiting run is normal, not a hang.
+- Never start a second run to "check" the first. Runs queue machine-wide by themselves (one at a time, or `CI_LOCAL_MAX_RUNS` / `maxRuns` in `~/.ci-local/config.json` at once, from 0.10.0); a waiting run is normal, not a hang.
 - Read the result from the run itself: `PASSED:` / `FAILED at step:` / `STOPPED` (stopped on purpose, not a failure) and `Development stack untouched`. A changed development stack is a failure.
 - On failure, read only the failing step's log (named in the failure output or `--status`), not every log.
 - Everything a run creates carries the `$CI_PROJECT` prefix and the `$CI_LABEL` label; never hard-code another name, publish a port, or reuse a development container name. Local compose smokes use `-p <own-name>`.
@@ -49,4 +49,4 @@ Report: project, commit, result line (`PASSED` / `FAILED at step` / `STOPPED`),
 
 ## References
 
-- Package README, "Following a run" and "One run at a time: the queue": events, `--status` states and exit codes.
+- Package README, "Following a run" and "One run at a time (or N): the queue": events, `--status` states and exit codes.