Release the shellcade-kit CLI from this repo#46
Merged
Conversation
The shellcade-kit binary used to be built by a separate downstream repo's GoReleaser in lockstep with the kit module tag. Move that mechanism here so the kit repo publishes its own CLI: - Add .goreleaser.yaml building ./cmd/shellcade-kit (cross-platform archives, checksums, and the Homebrew cask) and attaching them to this repo's vX.Y.Z release. Notarization stays gated behind the Apple secrets. - Add .github/workflows/release-cli.yml: on the changeset-produced vX.Y.Z tag, run GoReleaser, then fire a `kit-released` repository_dispatch (client_payload.version = the tag) to the consumer repos so they re-pin. - Rework ci.yml: the wasm / wasm-rust / release-wasm jobs now build the CLI from source instead of curl-fetching a pinned binary; drop the unused SHELLCADE_KIT_VERSION / SHELLCADE_KIT_SHA256 env. - Document the CLI release path in CLAUDE.md and add a changeset. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Port the catalog publishing-policy gate from the platform's main into kit's moved conformance + CLI copies, so it survives the platform migration merge. - conformance.LeaderboardVerdict(meta): static GameMeta check that a published game declares a LeaderboardSpec; deliberately NOT a generic ABI verdict (minimal fixtures legitimately declare none). - shellcade-kit check --require-leaderboard: opt-in flag that appends the verdict to the report; default check (and minimal fixtures) unaffected. - Test asserts the parity fixture (no board) fails under the strict check. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
BCook98
marked this pull request as ready for review
June 16, 2026 10:27
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
shellcade-kitCLI binary is now built and released directly from thisrepository, alongside the kit module tag. Previously the binary was produced by
a separate downstream GoReleaser run kept in lockstep with the module version.
What changed
.goreleaser.yaml(new) — builds./cmd/shellcade-kitfordarwin/linux/windows × amd64/arm64, produces the archives +
checksums.txt,and publishes the Homebrew cask (
brew install shellcade/tap/shellcade-kit).macOS signing/notarization stays gated behind the Apple secrets, so until
those exist releases ship unsigned (brew downloads are unaffected).
.github/workflows/release-cli.yml(new) — on thevX.Y.Ztag thechangesets flow pushes, runs GoReleaser to attach the binaries + checksums +
cask to that release, then fires a
kit-releasedrepository_dispatch(
client_payload.version= the tag) to the consumer repos so they can re-pintheir toolchain. The cross-repo token is supplied as
KIT_RELEASE_TOKEN..github/workflows/ci.yml— thewasm,wasm-rust, andrelease-wasmjobs now build the CLI from this PR's source (
go build -o shellcade-kit ./cmd/shellcade-kit) instead of curl-fetching a pinned release binary. Thenow-unused
SHELLCADE_KIT_VERSION/SHELLCADE_KIT_SHA256env was removed.CLAUDE.md— documents the CLI release path.kitpatch noting the CLI is now released from this repo.Required repository secrets
The release workflow expects these secrets on this repo:
KIT_RELEASE_TOKEN— token withcontents:writeonshellcade/kit(releaseassets) and
shellcade/homebrew-tap(cask push), and permission tosend
repository_dispatchto the consumer repos.MACOS_SIGN_P12,MACOS_SIGN_PASSWORD,MACOS_NOTARY_ISSUER_ID,MACOS_NOTARY_KEY_ID,MACOS_NOTARY_KEY— optional; notarization activatesonly when
MACOS_SIGN_P12is set.Verified locally
go build ./cmd/shellcade-kitandgo run ./cmd/shellcade-kit version.goreleaser checkpasses;goreleaser release --snapshot --clean --skip=notarizeproduces all six archives,checksums.txt, and the cask(cask URLs correctly resolve to this repo's releases).
actionlintpasses on both workflows.The full tagged release (publish + notarize + dispatch) needs secrets/a tag and
was not run locally.