Self-Hosting Weekly — August 12, 2026: Big betas, Arm arrives

Two of the biggest projects in the homelab stack moved this week: Jellyfin's 12.0 overhaul reached its fifth release candidate, and Proxmox VE picked up official Arm support. Gitea also shipped a patch release led by a security section, which makes this a good week to schedule a maintenance window.

Below: the three stories worth your attention, a stack of releases and betas, and a community project that keeps every video frame on your own network.

This Week's Highlights

Jellyfin 12.0 RC5 lands — start testing your migration now. The Jellyfin team announced the fifth release candidate of Jellyfin Server 12.0, explicitly labelled a preview release intended for people who want to test 12.0 ahead of its final public release. Read the release notes.

Why it matters: 12.0 is the largest media-server overhaul Jellyfin has attempted in years, and an RC5 usually means the stable tag is close. If you run Jellyfin as a daily driver for a household, the window to find out that your plugins or your database migration have a problem is now, on a copy — not on release day when three people are mid-episode.

The practical move: snapshot your config volume, spin up a second container against a cloned library, and check the plugins you actually depend on. RC builds are preview builds; the team is asking for testers, not for production deployments.

Close-up of server racks in a data center highlighting modern technology infrastructure.
Close-up of server racks in a data center highlighting modern technology infrastructure.

Proxmox officially supports Arm — with caveats. Jeff Geerling has the write-up on Proxmox VE's official Arm support, along with the asterisks that come with it. Read the post, or skim the Lobsters discussion.

This is a real shift for low-power homelab builds. Until now, running Proxmox on Arm meant unofficial ports and a tolerance for breakage. Official support puts Ampere boxes and Raspberry Pi-class hardware on the table as first-class hypervisor hosts — which changes the math for anyone who has been eyeing their electricity bill and their rack of aging x86 hardware.

Read the caveats before you order hardware, though. "Official" and "identical to x86" are not the same claim, and Geerling's post is where the boundaries are spelled out.

Gitea 1.27.1 fixes a security issue — patch it. The 1.27.1 patch release leads with a SECURITY section covering an orgmode render include path fix. See the release.

Self-hosted Git forges tend to sit on a trusted network segment holding every credential, deploy key and CI secret you own, which is exactly why a rendering-path bug is worth a same-week update rather than a next-quarter one. It's a point release; the upgrade should be uneventful.

New Releases & Updates

  • Nextcloud 35.0.0 beta 1 — the first beta of the next major Nextcloud branch, and the earliest look at Hub 35 for admins who plan upgrade windows well in advance. Release
  • Home Assistant 2026.8.0 — the monthly feature release for the most widely deployed self-hosted smart-home platform; 2026.8.1 followed within days with fixes, so update carefully or wait it out. Release · Blog post
  • n8n 2.35.0 — bug fixes for the self-hosted automation platform, including stopping pre-tool-call text from leaking into AI Agent node responses; 2.35.1 has already shipped patches on top. Release
  • Distro security updates (Tuesday) — patches from AlmaLinux, Debian and Fedora, notably Debian updates for caddy, nss and wordpress: three packages sitting right in the middle of most self-hosters' reverse-proxy and web stack. LWN roundup

Close-up of server racks in a data center highlighting modern technology infrastructure.
Close-up of server racks in a data center highlighting modern technology infrastructure.

Community Spotlight

A r/selfhosted regular rebuilt their live 3D print failure detector, and the pitch is about as on-brand as it gets for this audience: self-hosted, one container, and no frame ever leaves your network. Local-only inference is the detail that matters here — print monitoring normally means shipping a continuous camera feed of your workshop to somebody else's GPU, and this trades that away for a Docker-native deployment you fully control. If you have a printer running unattended and a spare bit of compute, it's worth a look. Read the thread.