Skip to content

fix: post-merge stability after go-deps #323 - #324

Draft
cursor[bot] wants to merge 1 commit into
masterfrom
cursor/overall-code-stability-13d3
Draft

fix: post-merge stability after go-deps #323#324
cursor[bot] wants to merge 1 commit into
masterfrom
cursor/overall-code-stability-13d3

Conversation

@cursor

@cursor cursor Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Summary

Post-merge stability review after Dependabot #323 (sentry-go 0.49.0, otel 1.46.0, grpc 1.83.1). The dependency bump itself is clean — no API breakage in Sentry, OpenTelemetry, or gRPC integration points.

Re-applies two unmerged stability fixes that block full master-push CI:

Type

  • fix — bug fix
  • chore — tooling, deps, repo hygiene

Testing

go build ./...
go test -short ./...
go vet ./...
# Full CI matrix: dashboard+open, landing, node SDK, python SDK (17 passed), mintlify, docs export, gosec, secret scan
  • Built locally
  • Tested affected endpoints/components

Deploy impact

  • Landing (hystersis.com)
  • Docs (docs.hystersis.com / /docs)
  • API (api.hystersis.com)
  • Dashboard (app.hystersis.com)
  • None (CI/Docker alignment only)

Agent notes

Go deps #323 review: all integration points (cmd/server/sentry.go, internal/telemetry/tracing.go, internal/memory/qdrant/client.go) verified — build, test, vet all green.

Open in Web View Automation 

After Dependabot #318 bumped the root Dockerfile to golang:1.27-alpine,
align the four service Dockerfiles (gateway, mcp-server, connectors,
memory-api) to the same builder image for consistent multi-service builds.

Exclude sdk/python/README.md from ruff format checks to prevent CI
failures on documentation code blocks (pre-existing issue on master).

Co-authored-by: Himan <Himan-D@users.noreply.github.com>
@trinetra-bote trinetra-bote Bot added the wip label Aug 31, 2026
@trinetra-bote

trinetra-bote Bot commented Aug 31, 2026

Copy link
Copy Markdown

⚠️ CI Check Trinetra Branch Protection failed. Please fix the build before merging.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
agent-memorydash a728e95 Aug 31 2026, 03:01 PM

@cloudflare-workers-and-pages

Copy link
Copy Markdown
Contributor

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
hystersis-docs a728e95 Aug 31 2026, 03:09 PM

@cloudflare-workers-and-pages

Copy link
Copy Markdown
Contributor

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
hystersis-app a728e95 Aug 31 2026, 03:05 PM

@cloudflare-workers-and-pages

Copy link
Copy Markdown
Contributor

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
agent-memory a728e95 Aug 31 2026, 03:12 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant