Summary
I received two bug reports via the Discordcserver. 1. The user couldn't add a book to their library via the Add New search. this was due to me consolidating some api endpoints and missing a few stragglers. 2. The user reported the app crashing agter a certain amount of time. I traced this back to a missing try catch on an exception in the download monitor.
Additionally in this release I added API versioning and fixed the login "Remember Me."
Added
- URL-segment API versioning support across backend routes (
/api/v{version}/...) with Swagger/ApiExplorer alignment. - Runtime API version exposure in startup config (
apiVersion) so the frontend can resolve version dynamically. - Centralized frontend API path/version helpers to build versioned endpoints consistently.
- Database-backed user session persistence (
UserSessions) with EF migration (20260301033814_AddPersistentUserSessions). - Swagger auth guidance to clarify how to authenticate and which endpoints require auth.
- Dev websocket proxy support for
/hubsto stabilize SignalR in local FE dev.
Removed
- Obsolete Audible/Amazon legacy controllers and endpoints (including legacy auth/library paths no longer used in canary).
- Legacy compatibility endpoint aliases/path normalization.
- Deprecated US-domain retry path/logic.
- Legacy Amazon scrape/search plumbing tied to removed Playwright-based flow.
Fixed
- Remember-me behavior now persists correctly across browser restarts and API restarts.
- Authenticated image loading regressions (ORB/placeholder issues, initial-load poster issues, Add New result images).
- Duplicate/looping image and metadata requests in Add New search results.
- Metadata add-flow crash paths when provider payloads are missing/invalid.
POST /api/v1/library/preview-pathpayload mismatch (metadata.isbnnormalization to expected array shape).- Router guard deprecation warnings (
next(...)callback usage). - Missing co...
Automated canary build