Skip to content

feat: deployment info in dashboard Signals panel#16

Merged
avrabe merged 2 commits intomainfrom
feat/deployment-signals
Mar 2, 2026
Merged

feat: deployment info in dashboard Signals panel#16
avrabe merged 2 commits intomainfrom
feat/deployment-signals

Conversation

@avrabe
Copy link
Contributor

@avrabe avrabe commented Mar 2, 2026

Summary

  • Surfaces deployed commit SHA, drift from main, commit diff, and remote branches in the dashboard Signals panel
  • Health endpoints (/health) now report the deploy SHA instead of hardcoded 1.0.0
  • Gracefully degrades: local info always renders, API-dependent section (drift, branches) wrapped in try/catch

Test plan

  • ESLint passes on all changed files
  • All 636 tests pass (updated 3 health endpoint assertions from exact '1.0.0' to expect.any(String))
  • Visual: http://localhost:3001/dashboard → Signals panel shows Deployment section with commit hash, drift status, and branches

🤖 Generated with Claude Code

Surface deployed commit SHA, drift from main, commit diff, and remote
branches in the Signals panel. Health endpoints now report the deploy
SHA instead of hardcoded 1.0.0.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@avrabe avrabe enabled auto-merge March 2, 2026 13:03
The pnpm-lock.yaml was never regenerated after better-sqlite3 was added
to package.json, so Bazel CI (which uses npm_translate_lock on the pnpm
lockfile) couldn't resolve the module. Also adds the dep to
src/BUILD.bazel and allows its native build scripts in pnpm config.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@avrabe avrabe merged commit b24a3d9 into main Mar 2, 2026
5 checks passed
@avrabe avrabe deleted the feat/deployment-signals branch March 2, 2026 13:22
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