viettranx dc482ff169 ci: run integration suite against pgvector service container ...

Integration tests were running locally only — CI never exercised
the 29 v3_*_test.go files under tests/integration/. This left the
session tenant-isolation + vault scan-arity bugs undetected until
a manual run this session.

Changes:
- tests/integration/v3_test_helper.go: testDB() now calls
  pg.InitSqlx(db) inside sharedDBOnce. Previously the test suite
  relied on whichever test ran first happening to call InitSqlx,
  so running with `-run <filter>` could segfault with a nil
  pkgSqlxDB. Removes the ordering-dependency land mine.
- .github/workflows/ci.yaml: add services.pg block running
  pgvector/pgvector:pg18 with pg_isready healthcheck, set
  TEST_DATABASE_URL at job level, and add a new "Integration
  tests" step after unit tests. Uses -timeout=180s (vs 90s unit)
  because the first test runs migrations from scratch.

Local integration suite: 2.9s. CI cold start expected ~30-60s
with image pull + migrations.

2026-04-12 07:18:01 +07:00

..

pr-assets

Release: credential resolver, WhatsApp native, exec hardening, traces UI (#754)

2026-04-08 15:56:18 +07:00

workflows

ci: run integration suite against pgvector service container

2026-04-12 07:18:01 +07:00

pull_request_template.md

chore: stabilize main branch with dev workflow + PR guidelines

2026-04-02 12:36:30 +07:00