Pin the CLI and plugin defaults to a matched 1.2.0-rc29 - #4
Open
asgeirf wants to merge 1 commit into
Open
Conversation
`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) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LSYPKgw58EVNrcE3fs5eV4
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The documented one-line adoption path could not push. Both reusable workflows installed a client that bowrain.cloud stopped serving on 21 August.
Two defaults, wrong in different ways
plugins: "bowrain"named no version. setup-kapi adds--channel betaonly when a ref carries a prerelease constraint, so a bare name resolves on stable, and the newest stable bowrain plugin is 1.1.0 (17 June). 1.1.0 POSTs<stream>/push/diff, which neokapi#2136 retired along with the server route. Every run failed on its first file.kapi-version: "1.2.0-rc14"was a hard-coded version from July. A stable promotion would not have moved it, so it needed a bump whatever happened to the channel.Both now name 1.2.0-rc29, so the CLI and the plugin come from one release rather than two versions that never met. The
@1.2.0-rc29on the plugin is what routes setup-kapi to the beta channel.Verified
manifest-plugins.json: every 1.2.0-rc ischannel: beta, newest stable is 1.1.0bowrain/core/client/push.go:302at tagv1.1.0bowrain/server/server.goroutes init/uploads/commit/chunks andGET /tree, and nothing else/pull,/status,/blocks,/push/init,/push/commit,/treeactionlintclean; defaults re-read from parsed YAMLFollow-up
When 1.2.0 ships stable, both defaults can move to 1.2.0 and the plugin ref can drop its channel constraint.
Separately, neokapi now answers the retired endpoint with 426 and an upgrade message instead of a bare 404, so a client pinned to an old version says why it failed rather than blaming the first file it sent.
🤖 Generated with Claude Code
https://claude.ai/code/session_01LSYPKgw58EVNrcE3fs5eV4