Release v0.27.0 · mfederowicz/tmdb-sync

What's Changed

account -v4 (needs -v4, read_access_token and a cached user token from auth -v4 -a login; no v3 session and no -i): -a lists, favorite-movies, favorite-tv, rated-movies, rated-tv, watchlist-movies, watchlist-tv, and the v4-only recommended-movies and recommended-tv. Results are written as account_<action>_v4.json.
account -v4 accepts -language <code> (favorites, rated, recommended, watchlist) and -sort-by created_at.asc|created_at.desc (favorites, rated, watchlist); using one where the endpoint doesn't take it, or without -v4, is an error.
lists -v4 (needs -v4 and read_access_token; everything except details also needs a cached user token from auth -v4 -a login): -a details (walks every item page, -language, -sort-by, -pages-limit), item-status (-media-type movie|tv, -media-id), and 🔒 create (-name, -language, -country, -description, -public), update (-name, -description, -public[=false], -sort-by, -backdrop-path), delete, clear, and the batch actions add-items, update-items (comment per item) and remove-items, which take repeatable -item movie:<id> / -item tv:<id>[:<comment>]. Results are written as lists_<action>_..._v4.json.

Internal refactor, no behavior change: the v4 auth service methods, tests and types now live in the v3 auth files (Client.Auth.*V4, str.RequestTokenV4/AccessTokenV4) instead of separate *_v4 files, matching how v4 account is laid out.

Full Changelog: v0.26.0...v0.27.0