v0.14.6
Bugfix
v0.14.6 - Live updates follow the switched account
Real-time updates follow the account you switched to, unresolved routing tokens no longer claim URLs, and several 500s become proper errors.
Fixes
- Real-time updates now target the account selected in the session rather than the user's oldest account.
- A content path containing an unresolved routing token (for example
:partwhen the entity field is not yet set) is no longer stored. The entry keeps its previous URL and gets the real one as soon as the field is set. - Concurrent
collections_savecalls creating the same handle: the loser now gets a conflict error instead of a 500. - REST asset upload: blank entries in the file list no longer cause a 500, and response keys stay contiguous.
- Visiting an account page with an id you do not belong to now redirects consistently on every account route.
- Model benchmarks stuck "generating" after a dead job become deletable after two hours of no progress.
Changes
- Custom domains record when the edge last accepted the host (
caddy_registered_at). Diagnostic only; it does not affect serving.