Repository navigation
·
103 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
Changes how /about lists modules and how the frontend connects to Reverb, fixes tasks/activity pagination and stale lazy chunks after upgrades, and replaces unmaintained Vue 2 frontend libraries.
Minor changes
- About page:
GET /aboutnow lists only enabled modules and reports them under their original names instead of lowercase registry keys. The stats collector still receives every installed module, enabled or not, with the original names. (#522) by @vermorag - Reverb connection: the frontend now takes the Reverb scheme and port from the page location (fixing
wss://host:80behind a TLS proxy;https→ 443,http→ 80, or the explicit page port) instead of the build-timeMIX_REVERB_SCHEME, which is no longer baked into the bundle. A build that relied on it to force the browser scheme must now serve the page over that scheme; an unusual public port is covered byMIX_REVERB_FRONTEND_PORT. (#520) by @vermorag
Patches
- Fixed
tasks/activitywithtype=allpaginating comments and history separately: the response now merges and orders the complete stream before paginating, so items and pagination metadata match and every entry is reachable. (#507) by @vermorag - Fixed the About page failing with
No such modulewhen the cached module list predates an installed module. The list is now rebuilt once, and a module whose version cannot be resolved is reported asdev. (#518) by @vermorag - Fixed lazy-loaded frontend chunks being served from a stale browser cache after an upgrade: chunk file names now include a content hash. (#519) by @vermorag
Maintenance
- Replaced the unmaintained Vue 2-only libraries
vue-kanban,vue-lazyload,vue-loading-skeleton,vue-avatarandvue-recaptchawith in-house components (dragulais now a direct dependency), in preparation for the Vue 3 / Vite migration. Behavior and appearance are unchanged, except that lazy images now request their screenshot URL only when they approach the viewport, and the login request is no longer lost when returning to the login page after the reCAPTCHA was shown. (#467) by @vermorag