Frigate NVR Updates: 0.18 Ships, 0.19 Begins

Frigate shipped its 0.18.0 release on September 12th, closing out a cycle that included interface cleanup and a bug fix around save attempt handling, while early groundwork for the 0.19 cycle has already opened with build and CI changes.

Duration: PT1M59S

Episode overview

This episode is a short developer briefing from Frigate NVR Updates.

It explains recent repository work in plain language.

  • Show: Frigate NVR Updates
  • Published: 2026-09-12T13:15:31Z
  • Audio duration: PT1M59S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good morning. It's September 12th, and this is Frigate NVR Updates.

The headline today is a release. Version 0.18.0 merged this morning, and it's the capstone on a short but focused run of pre-release cleanup work.

Two PRs from hawkeye217 set the stage. PR 24243 refactored the Notices and System Health pane, touching the app, API, and dispatcher layers - the kind of broad interface work that typically happens right before a release to make sure status and health reporting is solid for users. It went through a full review with…

Both of those fed directly into PR 24249, the 0.18.0 release itself, merged by blakeblackshear with support across camera, detector, and config documentation areas. That's your signal: the health pane rework and the save attempts fix were release hardening, not unrelated side work.

The second theme is what comes next. Just after 0.18 landed, NickM-27 opened PR 24251, labeled "0.19 Early Work." It's already touching build infrastructure - CI, the Makefile, Docker file, and the Go2rtc install step. That's foundational plumbing, not a feature. Worth watching as the next cycle takes shape, since…

What's next: expect 0.19 work to keep building out from that…

Nearby episodes from Frigate NVR Updates

  1. Face Recognition Gets a Rework and a Quick Follow-Up Fix
  2. Birdseye Flexibility Fix
  3. Visibility and Resilience Improvements
  4. Weekly Recap - System Health, Exports, and Hardware Reliability
  5. Fixing What's Broken at the Edges
  6. Interface Polish and a Hardware Decode Warning
  7. Export Flexibility and GPU Stability Fixes
  8. System Health Gets a Rework