gronod
d40646211f
Build and publish / Test and build (darwin) (push) Failing after 1m42s
Build and publish / Test and build (linux) (push) Failing after 1m53s
Build and publish / Test and build (windows) (push) Failing after 2m50s
Build and publish / Build and publish Docker image (push) Skipped
Go rewrite of the Python Emby.MCP server with tool parity (20 tools), plus a streamable-HTTP transport with per-request Emby authentication (Basic / Bearer token passthrough), a multi-arch Docker build, and a Gitea CI workflow.
530 B
530 B
Development guidance
Upstream endpoint changes
Every new or changed REST call in internal/emby must update the endpoint
manifest and known-issues registry in
internal/emby/spec_conformance_test.go. Add or update the corresponding row
in docs/api/endpoint_validation.md when the call inventory or findings
change. The conformance test is static; it does not require a live Emby
server.
Verification commands
go build ./...
go vet ./...
go test ./...
go test ./internal/emby/ -run TestSpecConformance -v