|

Vandalizer v4.5.0 Released

Vandalizer v4.5.0 just released: Here are the highlights

At a glance: 73 commits across 131 files – 14 new features, 12 bug fixes, and 3 security hardening changes.

Present & Pitch: A new “Overview” space for introducing Vandalizer to leadership, IT, and research teams. Each audience gets a skimmable page, a present-from-screen slide deck, and copy-paste elevator pitches. Print any of it to a PDF handout.

Your branding: Admins can set an org name and upload a logo (System Config → UI Theme). It appears across the header, login, footer, chat, and emails.

Per-user activity history: Super-admins can review any user’s full timeline (audit log + usage) in one view, with time-range filtering and CSV export.

Better setup & diagnostics: Connecting a language model now runs a real test and explains any failure in plain English with a suggested fix, plus a readiness checklist that guides you through anything unresolved.

Workflow improvements: A Stop button to cancel a running workflow mid-step, API-node templating ({{ inputs.output }}), inline credential creation, and the ability to test a Knowledge Base Query step on its own.

Reliability & security fixes: Resolved the intermittent “Connection error” in parallel workflows, a file-descriptor leak behind some production errors, support agents not seeing their tickets, mixed-case email login failures, and team invites accidentally demoting existing admins. Hardened secret fields against browser autofill and fixed CSRF issues during SSO sign-in.

Self-deployers: one required step: This release raises container memory limits (api 4G→8G, celery 8G→12G) to fix intermittent 502s caused by the kernel OOM-killing workers. The change requires recreating the containers, not just a restart: docker compose up -d api celery # or: ./setup.sh –redeploy

No new backend dependencies: Frontend dependency bumps are picked up automatically by Docker builds (rerun npm ci in frontend/ for manual builds). No .env/config changes needed.

Full details in CHANGELOG.md

-The AI4RA Team

Leave a Reply

Your email address will not be published. Required fields are marked *