Skip to content

fix: preserve API rate-limit errors#223

Open
skvark wants to merge 7 commits into
mainfrom
agent/align-api-rate-limit-errors
Open

fix: preserve API rate-limit errors#223
skvark wants to merge 7 commits into
mainfrom
agent/align-api-rate-limit-errors

Conversation

@skvark

@skvark skvark commented Jul 15, 2026

Copy link
Copy Markdown
Member

Summary

  • map API 429 and timeout responses to the shared structured error envelope
  • preserve standard Retry-After metadata without exposing response-body policy details
  • keep CLI JSON and MCP error behavior aligned and avoid automatic retries
  • use a longer client deadline for long-running example requests while retaining the standard deadline elsewhere
  • align plugin and Gemini descriptions with the current product positioning
  • add packed-package and published-metadata consistency coverage
  • bump githits to 0.6.3 and @githits/mcp to 0.6.2

Validation

  • bun test (2,441 passed)
  • bun run typecheck
  • bun run build
  • bun run lint (passes with one existing unrelated warning)
  • bun run validate:packages
  • targeted formatting checks for changed files
  • bun run smoke:mcp
  • bun run smoke:cli
  • direct live CLI/API verification confirmed 429 responses return promptly with the generic structured envelope

skvark added 7 commits July 15, 2026 11:16
Classify API rate-limit and timeout responses consistently across CLI and MCP consumers. Preserve standard retry metadata, keep public messages generic, and verify the behavior through packed package entrypoints.
Allow long-running example requests to complete without changing the standard deadline for shorter API operations. Preserve explicit timeout overrides for tests and embedding clients.
…limit-errors

# Conflicts:
#	packages/core-internal/src/services/githits-service.test.ts
#	packages/core-internal/src/services/githits-service.ts
#	src/commands/example.test.ts
Keep the CLI default at four minutes while allowing hosted transports to reserve time for their outer response boundaries.
Replace stale code-example-only positioning across plugin and Gemini metadata with the current product description. Add a consistency test so published manifests remain aligned with package metadata.
Split the Gemini context with a CRLF-aware expression so the description consistency assertion behaves identically on Windows and Unix runners.
Adopt the current GitHits product description across package, plugin, Gemini, CLI, README, and MCP registry surfaces. Extend consistency coverage to the README and server manifest.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant