Product changelog

Appearance

April 24, 2026 — Backend ​

Release date: Friday, April 24, 2026

Summary ​

Building APIs now expose a dedicated inspection summary shape in responses, with OpenAPI and list schema updated to match. A Prisma migration removes a legacy unique index on BuildingInspection.buildingId so the data model matches real inspection cardinality. Changelog workflow documentation moved to a renamed weekly-repo Cursor skill and the prior week’s backend recap was committed for continuity.

Shipped ​

  • Inspections in API responses: Inspection data mapped to a summary DTO on building responses; OpenAPI synced for inspection summary and list fields.
  • Database: Migration to drop the legacy BuildingInspection buildingId unique index (aligns schema with multiple inspections per building where applicable).
  • Docs & tooling: April 17, 2026 backend changelog file; Cursor skill renamed from weekly-commit-summary to weekly-repo-changelog with output path changelog/backend.

Engineering (commit recap) ​

Backend — week of April 21 – April 27, 2026 ​

Window: after 2026-04-18, before 2026-04-25 (--no-merges).

Summary ​

Building responses gained a structured inspection summary via a mapper and DTO, and OpenAPI was regenerated to reflect list and summary schemas. Prisma shipped a focused migration dropping an outdated unique index on building inspections. Housekeeping landed the previous Friday’s changelog artifact and refreshed the Cursor skill that generates these notes.

Themes ​

  • Building inspection API: Map inspections to a summary DTO in controller/service responses; keep DTOs and mappers consistent with domain types.
  • Contract & docs: OpenAPI sync for building inspection summary and list schema so clients see accurate shapes.
  • Schema & migrations: Remove legacy BuildingInspection.buildingId unique index; consumers should run the migration in order.
  • Release hygiene: Backend weekly changelog for April 17 committed; weekly-repo-changelog skill replaces weekly-commit-summary and targets changelog/backend.

Notable fixes or risks (if any) ​

  • Migrations: The unique-index drop changes database constraints—verify environments apply the migration before relying on multiple rows per building.
  • Clients: Regenerate or adjust API clients if they assumed the old inspection payload or uniqueness semantics.