Repository navigation
Add a Gemini CLI extension manifest - #250
Conversation
gemini-extension.json adds the swarmail MCP server through npx -y swarmail-mcp, so Gemini CLI can install the repository as an extension once a release contains it. The release check now fails when its version differs from package.json, and CONTRIBUTING lists the Gemini CLI extensions gallery, the version step and the order: release, then topic and README line.
|
Bompus AI Review could not run on 2871b67: no reviewer seat finished the review (GPT-6.1 Terra: daily credit stop, resets 11-12 00:00 UTC; GPT-6.1 Sol: daily credit stop, resets 11-12 00:00 UTC; Muse Wonder Full: usage limit reached; Gemini 4 Argon: usage limit reached, Gemini 4 Argon Weekly 100% until 11-14 23:30 UTC; SWE-2 Max: usage limit reached). Seats that may review this pull request, in order: GPT-6.1 Terra > GPT-6.1 Sol > Muse Wonder Full > Gemini 4 Argon > SWE-2 Max. If none of those finishes, a second seat may review alone: Gemini 3.8 Flash > Muse Wonder Full > Gemini 4 Argon > SWE-2 Max. Nothing was reviewed. The service tries this head again by itself after about 19:00 UTC; a new commit meets the same seats, so do not push one to retry. Merging before then needs the owner's exception. |
Set the version to 0.11.0 in package.json, packages/mcp-relay/package.json, gemini-extension.json and both server.json fields, and date the changelog section. The release covers #250: Gemini CLI can install the repository as an extension once the release exists. #246, #247 and #249 change nothing users run. The README line for the install command follows the release, so main never advertises a command that installs 0.10.0.
Set the version to 0.11.0 in package.json, packages/mcp-relay/package.json, gemini-extension.json and both server.json fields, and date the changelog section. The release covers #250: Gemini CLI can install the repository as an extension once the release exists. #246, #247 and #249 change nothing users run. The README line for the install command follows the release, so main never advertises a command that installs 0.10.0.
Set the version to 0.11.0 in package.json, packages/mcp-relay/package.json, gemini-extension.json and both server.json fields, and date the changelog section. The release covers #250: Gemini CLI can install the repository as an extension once the release exists. #246, #247 and #249 change nothing users run. The README line for the install command follows the release, so main never advertises a command that installs 0.10.0.
Adds
gemini-extension.jsonat the repository root, so Gemini CLI can install Swarmail as an extension once a release contains it. It adds theswarmailMCP server throughnpx -y swarmail-mcp, the same relay other registry-based clients use, and no hooks.versiondiffers frompackage.json(new case intest/release.test.ts, failing before the change).gemini extensions install https://github.com/bompus/swarmailworks only after a release contains the file. The README line and thegemini-cli-extensiontopic wait for that release. The README is unchanged here.Checked:
bun run checkandbun testpass (1546 tests). With gemini-cli 0.68.0 in a scratch home, installing the manifest from a local copy listedswarmail (0.10.0)with its MCP server, andgemini mcp listshowed Disconnected with no Swarmail server running and Connected against a throwaway server on port 18765.Not checked: a Gemini session calling a Swarmail tool, installing from the GitHub URL (needs a release), and the gallery crawler's validation.
evals/docs-checkwas not rerun, since the README is unchanged.