v1.4.0 — cloud dashboard populates end-to-end (config sync, pg_cron native scheduling, Edge Functions)

[johnoconnor0]

VGuard v1.4.0

Released: 2026-04-05
Install: npm install @anthril/vguard@1.4.0

What's Changed

Added

• Config-snapshot sync — the hook runner now pushes the resolved project configuration + CLI version to VGuard Cloud whenever the resolved config hash changes or 24h have passed since the last push. Populates projects.config_snapshot and projects.vguard_version, which lights up the dashboard's Active Presets, Quick Stats, Project Rules, Config Resolution Pipeline, and version-badge widgets. These widgets were empty for every project before this release because nothing in the CLI ever wrote to those columns. Override the endpoint host via VGUARD_FUNCTIONS_URL for self-hosted Supabase projects.
• vguard sync also pushes config snapshot after a successful rule-hits sync, as a manual fallback when hooks are disabled or haven't run recently.

Changed

• .husky/pre-commit skips the CHANGELOG/version-bump checks on merge commits (detected via .git/MERGE_HEAD). Merge commits consolidate existing history without introducing new entries, so blocking them forced empty CHANGELOG edits that added no value. Lint and type-check still run on every commit, including merges.

Fixed

• Cloud sync default URL now points to https://vguard.dev instead of the non-resolving https://api.vguard.dev / https://app.vguard.dev subdomains. Affected the streamer, CloudClient base URL, and the cloud login / cloud connect browser URLs. Override via VGUARD_CLOUD_URL.
• vguard cloud connect --key <vc_...> --project-id <id> now always persists credentials to ~/.vguard/credentials.json, even when run without a prior vguard cloud login. Previously the file was only updated if it already existed, leaving Claude Code hooks unable to read the API key and silently skipping real-time cloud streaming.
• Prettier formatting applied to 6 new rule and test files.

Cloud Updates

Ships alongside significant changes in vibe-guard-cloud that this release depends on:

• Native pg_cron scheduling for all analytics aggregation jobs. Six pure-SQL jobs (daily-summary, anomaly-detection, drift-snapshot, debt-prediction, sla-aggregate, benchmark-aggregate) now run directly inside Postgres on schedule. Previously these had no scheduler wired up at all, which is why daily_summaries was empty and the dashboard's timeline/heatmap/top-offenders widgets showed no data.
• Edge Functions for external-call crons (check-alerts, sla-ping, webhook-retry) triggered by pg_cron via net.http_post. The external Google Cloud Scheduler dependency is gone; every cron in the system is now scheduled from inside Postgres.
• ingest-config Edge Function — receives the config-snapshot push from this CLI release and writes it to the projects row.
• Vault-based pg_cron auth — pg_cron reads its Bearer token from vault.decrypted_secrets at job-run time, working within Supabase's managed superuser model (no manual alter database postgres set ... required).
• Critical fix: rule_hits dedup index drift — the production index included a COALESCE(file_path, '') expression that PostgREST's onConflict clause could not match, so every POST /api/v1/ingest call had been returning HTTP 500 INSERT_ERROR since production launch. Index rebuilt to exactly the five columns the API code passes.

Commits

vibe-guard (CLI, this release):

b43a0cd chore(release): v1.4.0 (#11)
e9e89a7 feat(cloud): push resolved config snapshot + CLI version to Cloud (#10)
a6e9de6 chore(ci): skip CHANGELOG + version checks on merge commits (#9)
a97069b fix(cloud): repair default URL and credential persistence for sync (#8)

vibe-guard-cloud (server, companion):

e6e6075 fix(cron): switch pg_cron Edge Function auth from GUC to Supabase Vault (#5)
a4864c8 feat(ingest): add Edge Function to receive project config snapshots (#4)
52adf37 feat(cron): migrate external-call crons to Supabase Edge Functions (#3)
0ffb2a5 feat(cron): schedule analytics aggregations via pg_cron (#2)
f462ca9 fix(db): rebuild rule_hits dedup index to match ingest onConflict spec (#1)

Upgrade notes

For existing consumers running 1.3.0:

npm install -D @anthril/vguard@^1.4.0
npx vguard generate

On the next Edit/Write in Claude Code, your resolved config will push automatically to the cloud dashboard. No config changes required — cloud.autoSync: true (the default) is all you need.

---

Full changelog: https://github.com/Anthril/vibe-guard/blob/master/CHANGELOG.md
npm: https://www.npmjs.com/package/@anthril/vguard/v/1.4.0
Release: https://github.com/Anthril/vibe-guard/releases/tag/v1.4.0