The Discourse on AWS by FOSSonCloud pattern now ships Discourse 2026.7.0, up from 2026.6.0 — a single monthly release cycle. July leaned heavily into live events and admin tooling, and there are no required migration steps.
What changed
- One-click livestream toggle on events. Creating an event with a URL now lets you enable livestream features in a single click. The stream link automatically previews (oneboxes) alongside the event, and livestream chat access is gated on event attendance.
- Unverified-user cleanup tools. The Admin → Users page gained a filter to surface unverified accounts on the New tab, plus a bulk-suspend action alongside the existing bulk-delete option.
- Cleaner notification emails. Notification emails dropped the prefixes, brackets, tags, and category annotations that used to clutter subject lines. This is an opt-in “upcoming change” you enable per site.
- Richer topic cards on the Horizon theme. Topic cards now show solved status, votes, assignee, tags, and excerpts.
Why it matters
The livestream flow is the feature with the most leverage. Running a live event on a Discourse community previously meant stitching together an event post, a stream link somewhere else, and a chat channel with no relationship to who actually showed up. Gating livestream chat on event attendance closes that loop — the people talking during the stream are the people who registered for it, which is both a moderation improvement and a better signal of real engagement.
The unverified-account tooling is unglamorous and genuinely valuable. Spam registration waves are a recurring problem for any public forum, and the previous workflow — no way to filter for unverified accounts, delete as the only bulk action — meant admins either spent an afternoon clicking or let the accounts pile up. Filter plus bulk suspend turns that into a two-minute job. Suspend rather than delete also matters: it’s reversible, so an aggressive cleanup that catches a legitimate user isn’t destructive.
The notification email change is small but affects deliverability and open rates. Subject lines cluttered with [Category] prefixes and tag annotations read as machine-generated, and some mail clients truncate them before the actual topic title appears. It’s opt-in because it changes what your members are used to seeing in their inbox.
What you should do
- Nothing is required. This release has no migration steps — it’s a normal-schedule update.
- Enable the cleaner notification email subjects deliberately. It’s opt-in per site. If you do enable it, tell your members, and check that any inbox filters they’ve built on the old bracketed subject format won’t silently break.
- Try the livestream toggle on your next event if your community runs them. The attendance-gated chat is the part worth testing — confirm the gating behaves the way your community expects before a high-profile event.
- Add the unverified-accounts filter to your moderation routine. Check the Admin → Users New tab periodically rather than only when a spam wave becomes visible, and prefer bulk suspend over bulk delete so mistakes stay reversible.
- Check the topic card changes if you run Horizon. More information per card is usually an improvement, but it changes list density — worth a look on mobile before your members mention it.
Version details in this post come from Discourse’s own release notes. If you hit anything upgrading the pattern, open an issue on GitHub.
— FOSSonCloud