Skip to content

Releases: GaijinEntertainment/go-gerrit-mcp

v1.1.3

Choose a tag to compare

@github-actions github-actions released this 15 Jul 13:20

Lowers the Go toolchain requirement: the module's go directive drops from 1.26.5 to 1.25.0, so go install
works on any Go 1.25 or newer toolchain instead of demanding the newest 1.26 patch. Nothing in the module needs Go
1.26; CI now tests every platform against both 1.25 and 1.26, and release binaries continue to be built with Go
1.26. No functional changes.

Changelog

v1.1.2

Choose a tag to compare

@github-actions github-actions released this 15 Jul 11:23

Fixes the registry manifest: the description now fits the registry's 100-character limit, making this the first
version whose registry entry published automatically end to end. No code changes; the server is functionally
identical to v1.1.1.

Changelog

v1.1.1

Choose a tag to compare

@github-actions github-actions released this 15 Jul 11:17

Breaking: get_change_comments defaults to unresolved threads

A bare get_change_comments call now returns only unresolved threads, the discussion that still needs action. On
long reviews the full comment history could overflow a client's tool-result limits, and the settled bulk is rarely
what the agent needs. Pass status=all for the previous behavior, or status=resolved for the settled threads
alone.

MCP registry publication

Releases now publish automatically to the official MCP registry as team.gaijin/go-gerrit-mcp, with domain
ownership proved over DNS. The registry manifest also documents the review-notifications flag family.

Note: this version's own registry entry never went live because the manifest description exceeded the registry's
length limit; v1.1.2 fixes that. Binaries and the container image of v1.1.1 are unaffected.

Changelog

v1.1.0

Choose a tag to compare

@github-actions github-actions released this 15 Jul 09:17

Review notifications

This release adds an opt-in push channel for review activity. An agent subscribes to a change with the new
subscribe_change tool; new change messages, votes, comment threads, and status transitions then arrive in the
session on their own, so the agent no longer polls the read tools while waiting for a review outcome.

  • subscribe_change and unsubscribe_change tools, registered only when the feature is on.
  • One batched Gerrit query per poll tick regardless of subscription count, with detail fetches only for changes
    that actually moved.
  • Payloads carry the activity whole, in the same llmxml vocabulary the read tools emit; comment threads render
    exactly as get_change_comments shows them.
  • Subscriptions end themselves when a change is merged or abandoned, announced by a final notification. A change
    that stops being readable ends its subscription the same way, with the reason spelled out.
  • Noise control stays with the operator: own activity is skipped by default (--review-notifications-include-own
    keeps it), and accounts or message patterns can be excluded. Nothing is filtered by message tag, because a bot's
    verdict is often exactly the outcome the agent waits for.
  • Delivery uses the Claude Code channels contract (research preview, Claude Code 2.1.80 or newer). A client without
    channel support silently drops the events and the server behaves as if the feature were off.
  • With the feature off (the default) the server is byte-identical to v1.0.0: same tools, same capabilities, no
    background polling.

New flags: --review-notifications, --review-notifications-poll-interval (default 60s),
--review-notifications-include-own, --review-notifications-exclude-accounts, and
--review-notifications-exclude-patterns, each with a GERRIT_MCP_* environment mirror. The README covers
client-side enablement and the research-preview caveats.

Changelog

v1.0.0

Choose a tag to compare

@github-actions github-actions released this 13 Jul 13:50

Changelog

v0.1.0

Choose a tag to compare

@github-actions github-actions released this 10 Jul 23:19

Changelog