⚠️ Behavior change (#121): config schema validation now hard-fails
An invalid config.json now stops the service at startup with a single aggregated, actionable message, instead of warning and continuing. In a container this surfaces as the container failing to start / restarting.
- Applies to schema rule violations: wrong type, out-of-range, missing required field, bad format/pattern, invalid enum.
- Unknown / typo'd keys stay advisory (warn only) and are ignored at runtime, so they do not block startup.
- Escape hatch: set
CONFIG_STRICT=false(or0/no/off) to temporarily downgrade these to warnings during a migration. - Before upgrading: run
npm run validate-configto check your config; if a container will not start after upgrade, check the logs for the validation error and fixconfig.json.
See docs/CONFIG.md (Schema Validation) for details.
Full Changelog: v1.8.8...v1.9.0