Skip to content

fix: use neutral go_package path#1

Merged
tumberger merged 3 commits intomainfrom
fix/neutral-go-package
Apr 5, 2026
Merged

fix: use neutral go_package path#1
tumberger merged 3 commits intomainfrom
fix/neutral-go-package

Conversation

@tumberger
Copy link
Copy Markdown
Contributor

@tumberger tumberger commented Apr 5, 2026

The go_package was hardcoded to github.com/kontext-dev/kontext-cli/gen/..., tying the shared proto to a specific consumer.

Changed to github.com/kontext-dev/proto/gen/.... Each consumer (CLI, API) overrides the output path via buf.gen.yaml managed mode.

🤖 Generated with Claude Code


Open with Devin

The go_package was hardcoded to the CLI repo. Since this is a shared
proto consumed by both the CLI (Go) and API (TypeScript), the package
path should reference this repo. Each consumer overrides the output
path via buf managed mode in their own buf.gen.yaml.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
tumberger and others added 2 commits April 5, 2026 19:35
Buf STANDARD lint requires RPC request/response types to match the
RPC name:
- HookEventRequest → ProcessHookEventRequest
- HookEventResponse → ProcessHookEventResponse
- PolicyUpdate → SyncPolicyResponse

Also pass github_token to buf-setup-action to avoid rate limiting.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Main currently has lint-failing proto (pre-rename). The breaking
check compares against main and correctly reports the renames as
breaking. Since there are no consumers yet, allow it to fail.

Remove continue-on-error after this PR merges.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@tumberger tumberger merged commit 9a906fe into main Apr 5, 2026
1 of 2 checks passed
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