From 09f1a95a1129ac33181b8963320b1c038ced93e9 Mon Sep 17 00:00:00 2001 From: Asgeir Frimannsson Date: Fri, 28 Aug 2026 13:03:48 +0200 Subject: [PATCH] Pin the CLI and plugin defaults to a matched 1.2.0-rc29 `plugins: "bowrain"` carried no version, and setup-kapi adds `--channel beta` only when a ref names a prerelease, so it resolved on stable. The newest stable plugin is 1.1.0 from June, which sends the push protocol bowrain.cloud retired in August: every run of the documented path failed its first push. `kapi-version` was a stale 1.2.0-rc14 that a stable release would not have moved, so it needed pinning either way. Both now name 1.2.0-rc29, which is one released pair rather than two versions that never met. Revisit when 1.2.0 ships stable: both defaults can move to 1.2.0, and the plugin ref can drop its channel constraint. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01LSYPKgw58EVNrcE3fs5eV4 --- .github/workflows/gate.yml | 14 +++++++++++--- .github/workflows/up.yml | 14 +++++++++++--- 2 files changed, 22 insertions(+), 6 deletions(-) diff --git a/.github/workflows/gate.yml b/.github/workflows/gate.yml index 1873e0a..5ea4a26 100644 --- a/.github/workflows/gate.yml +++ b/.github/workflows/gate.yml @@ -28,13 +28,21 @@ on: type: string default: "--ship" plugins: - description: "Plugin refs for setup-kapi (registry names)" + description: "Plugin refs for setup-kapi (registry names, each optionally @version)" type: string - default: "bowrain" + # Pinned, and pinned to a prerelease on purpose. setup-kapi passes + # `--channel beta` only when a ref carries a prerelease constraint, so a + # bare `bowrain` resolves on stable, and stable stays at 1.1.0 until + # 1.2.0 ships. A 1.1.0 plugin sends the push protocol the server + # retired, and bowrain.cloud answers 426 telling you to upgrade. + default: "bowrain@1.2.0-rc29" kapi-version: description: "kapi CLI version. `check --ship` ships in 1.2.0; until 1.2.0 is stable this pins the release candidate" type: string - default: "1.2.0-rc14" + # Kept at the same version as the plugin above: the two share the + # framework and cli modules, so a matched pair is the pair that was + # tested together. + default: "1.2.0-rc29" pr-comment: description: "Sticky report comment on pull-request events" type: boolean diff --git a/.github/workflows/up.yml b/.github/workflows/up.yml index e479526..3573ac6 100644 --- a/.github/workflows/up.yml +++ b/.github/workflows/up.yml @@ -33,13 +33,21 @@ on: type: boolean default: false plugins: - description: "Plugin refs for setup-kapi (registry names)" + description: "Plugin refs for setup-kapi (registry names, each optionally @version)" type: string - default: "bowrain" + # Pinned, and pinned to a prerelease on purpose. setup-kapi passes + # `--channel beta` only when a ref carries a prerelease constraint, so a + # bare `bowrain` resolves on stable, and stable stays at 1.1.0 until + # 1.2.0 ships. A 1.1.0 plugin sends the push protocol the server + # retired, and bowrain.cloud answers 426 telling you to upgrade. + default: "bowrain@1.2.0-rc29" kapi-version: description: "kapi CLI version. `kapi up` ships in 1.2.0; until 1.2.0 is stable this pins the release candidate" type: string - default: "1.2.0-rc14" + # Kept at the same version as the plugin above: the two share the + # framework and cli modules, so a matched pair is the pair that was + # tested together. + default: "1.2.0-rc29" server: description: "Bowrain server URL (exported as BOWRAIN_SERVER_URL)" type: string