Repository navigation
Aggregato 1.0.0
- Add a Spotify recently-played provider and a Media view for browsing works.
- Restrict archives and operational diagnostics to operators. Read-only run summaries hide logs,
detailed errors, and cursors; response diagnostics retain only the method, sanitized endpoint,
and status. - Preserve valid data when normalization replay encounters a bad record or is interrupted, and
retain manual creator splits through resync and merge/undo operations. Failed full runs cannot
infer deletions. - Enforce one scheduler worker per database and bound shutdown while provider children are cleaned
up. Suspended history syncs resume only after an explicit enable, sync, or valid configuration
change; checks and queued imports or replays remain available while disabled. - Apply title and review search before pagination, preserve indexed keyset bounds for deep pages,
and calculate weekly statistics by ISO week. - Improve correction feedback, undo state, provider-check polling, settings, and session-aware live
updates. Show when instance configuration locks image caching while preserving its saved
preference, and report payload estimates and SQLite file size. - Support WebSocket upgrades through the production proxy, release idle handlers on disconnect,
contain backend static-file paths, and include the PostgreSQL driver in the backend image. - License the project under AGPLv3 and add private vulnerability reporting; update provider,
operations, and release guidance and remove stale specifications.
Upgrade and data handling
The API applies pending migrations automatically at startup. This release adds forward-only
migrations 0019, which preserves
provenance for existing manual creator splits, and 0020,
which indexes entry lookups by provider item. SQLite creates a pre-migration backup when an upgrade
is pending; PostgreSQL does not, so take a native backup before upgrading.
The portable archive is available only for on-disk SQLite. It omits configured credentials, sessions, queued
jobs, failure payloads, diagnostics, and cursor state, but still contains personal history and
retained provider payloads. Keep archives private. Full database backups can also contain
credentials and sessions and should remain private. Feed and recently-played sources expose limited
windows; a full resync cannot recover history the source no longer supplies. See the
provider table and operations guide for details.