v2.8.1
Agregarr now requires one of its own labels before it will touch a collection, plus hardening around how releases are versioned.
Docker tags
| Tag | What it tracks |
|---|---|
bitr8/agregarr:latest
| Stable releases. This is what you want. |
bitr8/agregarr:2.8.1
| Pinned to this exact release. |
bitr8/agregarr:develop
| Bleeding edge. Builds on every push, breaks sometimes. |
Upgrading from 2.8.0 is just a pull; config volumes are compatible. Release tags ship amd64 and arm64.
Fixed
Collection ownership is decided by label, not by name
When a config lost track of its collection in Plex, it fell back to matching on title without checking whether the collection was Agregarr's. A collection of your own with the same name as one of your configs could be adopted: relabelled, its contents replaced, its smart filter overwritten. A config set to remove its collection when inactive could delete it.
An agregarr label is now the only thing that marks a collection as Agregarr's, and it's checked at all five places that matched on title: the main collection lookup, the multi-source name fallback and its inactive-delete path, and the separator and person lookups. An unlabelled collection is left alone and Agregarr creates its own.
Present in 2.8.0 and earlier. You no longer need to keep your own collection names distinct from your config names.
A collection's rating key is now stored as soon as Plex returns it, before items, metadata and labelling. A collection that was created but never labelled is found by that key on the next sync and relabelled, instead of being left behind and duplicated.
Release versioning
The version the app reports now comes from the git tag at build time, and the release build fails if the version in the image and the tag disagree.
2.8.0 images report 2.7.0 under the old process. That also left :latest and :2.8.0 showing "update available" permanently, since the check compares the reported version against the newest release name. Pulling 2.8.1 clears both.
Develop builds report develop-<sha> again and compare commits rather than releases, so their update check clears when they're current.
Known and unfixed
- Two configs in the same library whose collection names render the same can act on each other's collection. The label shows a collection is Agregarr's, not which config it belongs to.
- A targeted collection that's promoted to the Home screen still shows on everyone's Home. Plex has no per-user version of that switch.
- Person collections get deleted on the next cleanup pass if their title template renders anything other than the plain person name. Cleanup matches on the bare name.
- Restoring a base poster larger than 1000x1500 downscales it. Movies and shows too, not just seasons.
- Restored posters stay locked in Plex.