Skip to content

chore(deps): update adguard/adguardhome docker tag to v0.107.80 - #715

Merged
doa-renovate[bot] merged 1 commit into
mainfrom
renovate/adguardhome
Nov 3, 2026
Merged

doa-renovate[bot] merged 1 commit into
mainfrom
renovate/adguardhome

Conversation

@doa-renovate

@doa-renovate doa-renovate Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
adguard/adguardhome (source) patch v0.107.79 → v0.107.80

Release Notes

AdguardTeam/AdGuardHome (adguard/adguardhome)

v0.107.80

Compare Source

See also the v0.107.80 GitHub milestone.

NOTE: Add new changes BELOW THIS COMMENT.
-->

Security
  • Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.27.3.
Changed
  • Client settings in the new web interface: Use global settings now applies to Protection only, blocked services have a separate Use global blocked services switch, and upstream DNS servers and the DNS cache are always editable.
Fixed
  • Invalid SVCB record from DDR when DoH routes are empty.

  • Schedule shift on clock change cases (#​8670).

  • Incorrect behaviour on the first launch with the --check-config flag.

  • Reading partially received TCP prefix.

  • A panic when updating AdGuard Home binary via the command line with use_private_ptr_resolvers set to true (#​8613).

  • log.enabled set to false leaving the legacy logger enabled (#​8565).

  • DHCP server persisting uncommitted leases with zero expiry after DHCPDISCOVER messages (#​8572).

  • DHCPv4 settings not being saved when an IPv6-capable interface is selected and DHCPv6 is not configured (#​8608).

  • DHCP not being enabled when only the DHCPv6 section is configured.

  • DHCP IPv4 range subnet validation not working (#​8609).

  • Client ID validation rejecting valid IPv6 CIDRs with an embedded dotted-decimal IPv4 address (#​8610).

  • Client ID validation accepting IPv4 addresses with leading-zero octets (192.168.01.1), malformed MAC addresses, and ClientIDs with leading or trailing hyphens.

  • IP addresses being sorted lexicographically instead of numerically in the web interface (#​8636).

  • Invalid secondary bootstrap resolver IPv4 address (#​8637).

  • The Server addresses dialog overflowing horizontally when a long value is entered. Long unbreakable values in the settings rows overflowing the page.

  • Encrypted DNS server addresses not appearing in the Setup Guide until the page was reloaded after enabling encryption.

  • Passwords containing emoji being rejected by the first-run setup wizard in the new web interface.

  • Cache size and TTL override rows being locked while the DNS cache was disabled in the new web interface (#​8644).

  • Tables staying on an empty page after the last row of that page was deleted in the new web interface (#​8644).

  • The Log out button opening the login page in a new tab in the new web interface (#​8661).

  • Per-client blocked services schedules being reset when a client was saved in the new web interface (#​8638).

  • Client sub-pages of the new web interface showing the default values instead of the client's settings when opened directly or reloaded.

Removed

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@doa-renovate
doa-renovate Bot requested a review from 5ym November 3, 2026 13:20
@doa-renovate
doa-renovate Bot merged commit 5ab826c into main Nov 3, 2026
4 checks passed
@doa-renovate
doa-renovate Bot deleted the renovate/adguardhome branch November 3, 2026 13:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants