VERSIONS.json

{
  "project": "ems-core",
  "project_version": "1.4.1",
  "last_updated": "2026-04-06",
  "notes": "Add alembic migration 009 for ai_ops/strategy/weather/prediction tables"
}
feat!: backend-only architecture, remove frontend/nginx (v1.2.0) - Remove frontend/ and nginx/ from core (each customer owns their frontend) - Update docker-compose.yml to backend-only (postgres + redis + backend) - Update docker-compose.prod.yml to backend-only - Add CLAUDE.md with dev guidelines - Update README.md with new architecture diagram Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> 2026-04-05 23:39:31 +08:00			`{`
			`"project": "ems-core",`
fix(models): add alembic migration 009 for missing tables (v1.4.1) Migration adds tables that existed in models/ but were never included in alembic history: - ai_ops: device_health_scores, anomaly_detections, diagnostic_reports, maintenance_predictions, ops_insights - energy_strategy: tou_pricing, tou_pricing_periods, energy_strategies, strategy_executions, monthly_cost_reports - weather: weather_data, weather_config - prediction: prediction_tasks, prediction_results, optimization_schedules Without this migration, fresh deploys would 500 on these endpoints: - /api/v1/ai-ops/health, /ai-ops/dashboard - /api/v1/strategy/pricing - /api/v1/prediction/forecast - /api/v1/weather/current Discovered during Z-Park demo deployment on xie_openclaw1. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> 2026-04-10 09:47:34 +08:00			`"project_version": "1.4.1",`
fix: update VERSIONS.json to match v1.2.0 tag VERSIONS.json was still showing 1.1.0 while the git tag and commit message already referenced v1.2.0. Sync version metadata. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> 2026-04-06 08:21:15 +08:00			`"last_updated": "2026-04-06",`
fix(models): add alembic migration 009 for missing tables (v1.4.1) Migration adds tables that existed in models/ but were never included in alembic history: - ai_ops: device_health_scores, anomaly_detections, diagnostic_reports, maintenance_predictions, ops_insights - energy_strategy: tou_pricing, tou_pricing_periods, energy_strategies, strategy_executions, monthly_cost_reports - weather: weather_data, weather_config - prediction: prediction_tasks, prediction_results, optimization_schedules Without this migration, fresh deploys would 500 on these endpoints: - /api/v1/ai-ops/health, /ai-ops/dashboard - /api/v1/strategy/pricing - /api/v1/prediction/forecast - /api/v1/weather/current Discovered during Z-Park demo deployment on xie_openclaw1. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> 2026-04-10 09:47:34 +08:00			`"notes": "Add alembic migration 009 for ai_ops/strategy/weather/prediction tables"`
feat!: backend-only architecture, remove frontend/nginx (v1.2.0) - Remove frontend/ and nginx/ from core (each customer owns their frontend) - Update docker-compose.yml to backend-only (postgres + redis + backend) - Update docker-compose.prod.yml to backend-only - Add CLAUDE.md with dev guidelines - Update README.md with new architecture diagram Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> 2026-04-05 23:39:31 +08:00			`}`