Changes
🛠️ Bug Fix Release - Config Schema Upgrade Hotfix
Overview
Critical hotfix resolving 500 errors on /v1/config endpoint affecting users upgrading from v0.7.2 to v0.7.3/v0.7.4 with existing databases (fixes #769).
Key Updates
Critical Bug Fix
- Fixed upgrade failures: Resolved "Response doesn't match the schema" errors preventing config page access after upgrade (fixes #769)
- Root cause: Schema changes in v0.7.3 made nested config fields required, but database JSON could contain partial objects from prior versions
- Impact: Users upgrading from v0.7.2 with partial config stored in database experienced config endpoint failures
Technical Changes
- Applied deep merge pattern for nested config objects (
quotaSettings,plexLabelSync) to ensure all required fields exist - Applied shallow spread pattern for flat config objects (
publicContentNotifications,approvalExpiration) - Fixed type literal mismatches between schema and implementation (
handleMonthEnd,removedLabelMode) - Applied consistent defaults across both database reads and environment initialization
Migration & Compatibility
No migration required - code-only fix ensures backward compatibility with partial config JSON from v0.7.2 databases.
Docker users - Pull latest image: lakker/pulsarr:0.7.5
Manual installation users - Standard update process applies
Full Changelog: v0.7.4...v0.7.5
Docker Image: lakker/pulsarr:0.7.5
Docker
docker pull lakker/pulsarr:0.7.5