Shankar 716a0f2958 fix: migration runner only executes .up.sql files, skips .down.sql and seeds ...

The migration runner was collecting all .sql files alphabetically, which
caused .down.sql rollback files (DROP TABLE) to execute before .up.sql
files on restart with a persisted postgres volume. Filter to only .up.sql
files — these are idempotent (IF NOT EXISTS) and safe to re-run.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-03-24 12:08:12 -04:00

..

api

fix: remove unused import and variable flagged by go vet

2026-03-24 01:07:16 -04:00

cli

feat: M17 OpenSSL/Custom CA issuer connector + M16b CLI tool with bulk import

2026-03-23 18:12:40 -04:00

config

feat: M17 OpenSSL/Custom CA issuer connector + M16b CLI tool with bulk import

2026-03-23 18:12:40 -04:00

connector

feat: M17 OpenSSL/Custom CA issuer connector + M16b CLI tool with bulk import

2026-03-23 18:12:40 -04:00

domain

fix: remove unused import and variable flagged by go vet

2026-03-24 01:07:16 -04:00

integration

feat: M18b Filesystem Certificate Discovery — agent scanning, server dedup, triage API

2026-03-24 00:25:00 -04:00

mcp

fix: Go 1.25 upgrade, codebase audit fixes, MCP server tests

2026-03-23 17:36:25 -04:00

repository

fix: migration runner only executes .up.sql files, skips .down.sql and seeds

2026-03-24 12:08:12 -04:00

scheduler

feat: M11a — certificate profiles, crypto policy enforcement, short-lived cert expiry

2026-03-20 20:39:49 -04:00

service

feat: M18b Filesystem Certificate Discovery — agent scanning, server dedup, triage API

2026-03-24 00:25:00 -04:00