Repository navigation
ci: release-please and release binaries #12
Description
Part of #2. Release automation, matching Go's release-please.yml, release-please-config.json and build-release.yml at 9e072f9.
Do
- release-please:
release-please-config.jsonwithrelease-type: rust,include-v-in-tag: true,bump-minor-pre-major: trueandbump-patch-for-minor-pre-major: true, for the plugin crate..release-please-manifest.jsonstarting at0.0.0.- The workflow runs on pushes to
main, using theTOKEN_BOT_GITHUB_TOKENsecret like Go's, so that release PRs trigger CI. - Use
extra-files(or a workspace setup) if needed so the plugin'sCargo.tomlversion andCargo.lockare bumped together.
- Release binaries: on
release: created, buildprotoc-gen-rust-mcpfor linux, macos and windows × x86_64 and aarch64 (native runners orcross), and attach.tar.gz(or.zipon windows) archives plus a SHA-256 checksums file to the release.- The binary's
--versionmust report the released version.
- The binary's
- This issue asks you to change
.github/workflows/**. Don't publish to crates.io (out of scope).
Acceptance criteria
-
actionlint(or an equivalent) is clean on the new workflows. - The release-binaries workflow can also be triggered with
workflow_dispatchas a dry run that uploads the archives as workflow artifacts. Run it once on the PR branch and link the run. - If the
TOKEN_BOT_GITHUB_TOKENsecret isn't available in this repo, say so in the PR and ask (factory:question); don't fall back silently toGITHUB_TOKEN.
Activity
erikist commentedon Oct 9, 2026
🤖 Factory: picked up by dispatcher; working on branch factory/12-ci-release-please-and-release-binaries.
ci: pin release-please-action, tighten permissions, verify --version (#…
erikist commentedon Oct 9, 2026
🤖 Factory: opened PR #17 with the release-please and release-binaries workflows.
Two things from the acceptance criteria need a maintainer's input (details in the PR body):
TOKEN_BOT_GITHUB_TOKENdoesn't exist as a repository secret today (0 repo secrets found via the API; I can't check org-level secrets). The workflow fails fast with a clear error rather than falling back to the default token — could someone confirm/add the secret?workflow_dispatchdry run can't be exercised before this PR merges — GitHub only allows dispatching workflow files that already exist on the default branch. I'll trigger it againstmainright after merge and link the run.See #17 for the full summary, test evidence, and design decisions (notably using
release-type: "simple"+extra-filesinstead of"rust", due to an open upstream release-please bug withversion.workspace = true).ci: run release-please in the release environment (#12)
ci: release-please and release binaries (#12) (#17)
erikist commentedon Oct 9, 2026
🔍 Post-merge dry run of
release-binaries.ymlonmain(workflow_dispatch): https://github.com/stablekernel/protoc-gen-rust-mcp/actions/runs/37981192010. All 6 platform builds andpackagesucceeded, andrelease-archiveswas uploaded with the archives andchecksums.txt. Still to do: a maintainer addsTOKEN_BOT_GITHUB_TOKENto thereleaseenvironment. Until then,release-pleasefails on every push tomain, by design.