Releases · AdGuard Home

AdGuard Home's beta channel jumps to 1.0.0 and switches to the new UI

The beta channel moves from 0.108.0-b.91 to the project's first 1.0.0 build, bringing the new UI, a Go security bump, four small fixes, and the end of macOS 13 support.

By BoneWednesday 30 September 20262 min readReleases

entryread only

filedWednesday 30 September 2026

length2 min

sectionReleases

subjectAdGuard Home

sourceson the page

AdGuard Home’s beta channel jumped on September 30 from 0.108.0-b.91 to 1.0.0-b.1, the project’s first 1.0.0 build after a long run of 0.107.x releases. The release notes explain both the number and the visible change in one line: “The beta channel has been switched to the new UI and versioning scheme.” The edge channel made the same move with August’s release; beta is where the switch reaches the people who actually test.

The project runs two unstable channels alongside stable, and the readme is plain about the difference: beta carries “more or less stable versions, usually released every two weeks or more often”, while edge is the daily build from the development branch. This release switches the middle lane, not the daily one.

What is in it

Compared with the previous beta, v0.108.0-b.91, the notes run to four short sections. Security: a Go update to 1.27.1, which carries the fixes for the vulnerabilities closed in that release. Fixed, according to the notes: reading partially received TCP prefixes, and a panic when the binary is updated from the command line with use_private_ptr_resolvers turned on (issue #8613), the kind of setup that shows up on networks with local PTR lookups. The changelog adds two more small fixes: log.enabled set to false was leaving the legacy logger running (#8565), and the DHCP server persisted uncommitted leases with a zero expiry after DHCPDISCOVER messages (#8572). Removed: macOS 13 Ventura, following Go 1.27’s own cutoff.

1.0 does not mean stable

The stable channel still serves 0.107.x, with 0.107.79 from mid-August as the newest, and nothing in this build argues for moving the resolver your household depends on onto a beta. The version jump is about the release line, not about the code suddenly being finished. The new UI is the same one edge testers have had since August, the fix list is small, and nothing here migrates a database or reworks a configuration file. It is a direction change, not a feature drop.

My read

If you have been looking for a moment to try the beta channel, this is the natural one, because the versioning finally reads 1.0. But it is still the beta channel. The sensible shape for most homes is unchanged: run testing builds somewhere you can afford to lose DNS for an hour, keep the household resolver on stable, and treat the eventual stable 1.0.0 as the release that earns a maintenance window. The Go bump is worth taking whenever it reaches your channel.

Source: the v1.0.0-b.1 release and the changelog at that tag.

ReleasesHomebridge 2.5.0 is a Matter release: new device types, and fixes for identity and cacheHomebridge 2.5.0 adds Matter device types for solar, battery, EV chargers, meters, tariffs and water heaters, and spends the rest of its list on behaviour that used to go wrong: air quality reporting only two levels, thermostats registering late, restored accessories losing their uniqueId or owner, and cache reads that took the accessory with them. It also bumps @matter/main to v0.18.0 and @homebridge/hap-nodejs to v2.3.0.

ReleasesMealie 3.30.0 lets you own the AI prompt, time each step, and plan a whole weekMealie 3.30.0 moves AI prompt control into the app, so prompts can be appended to, replaced or extended with global instructions, and it retires the OPENAI_CUSTOM_PROMPT_DIR variable while importing existing prompts automatically. Instruction steps gain individual durations, meal plan entries can cover a full week, and a batch of fixes tightens import scoping, locale lookup and the permissions needed to manage units, tools, labels and recipe actions.

ReleasesMemos 26.10.0 signs API clients out, stops reading /etc/secrets and makes export an admin jobMemos 26.10.0 is the first release under calendar versioning, and its upgrade notes matter more than its features: old installs need a 0.31.0 waypoint, cached access tokens expire on upgrade, the /etc/secrets files from 0.31.0 are no longer read, member export disappears, and the old upload and memo-length settings are replaced without migration. The features are a rich editor by default, per-user usage limits and declarative configuration.