Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update adguard/adguardhome Docker tag to v0.107.50 #173

Merged
merged 1 commit into from
Jun 3, 2024

Conversation

chemical-soup
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
adguard/adguardhome (source) final patch v0.107.48 -> v0.107.50

Release Notes

AdguardTeam/AdGuardHome (adguard/adguardhome)

v0.107.50

Compare Source

See also the v0.107.50 GitHub milestone.

Fixed
  • Broken private reverse DNS upstream servers validation causing update failures
    (#​7013).

v0.107.49

Compare Source

See also the v0.107.49 GitHub milestone.

Security
  • Go version has been updated to prevent the possibility of exploiting the Go
    vulnerabilities fixed in Go 1.22.3.
Added
  • Support for comments in the ipset file (#​5345).
Changed
  • Private rDNS resolution now also affects SOA and NS requests (#​6882).
  • Rewrite rules mechanics were changed due to improved resolving in safe search.
Deprecated
  • Currently, AdGuard Home skips persistent clients that have duplicate fields
    when reading them from the configuration file. This behaviour is deprecated
    and will cause errors on startup in a future release.
Fixed
  • Acceptance of duplicate UIDs for persistent clients at startup. See also the
    section on client settings on the [Wiki page][wiki-config].
  • Domain specifications for top-level domains not considered for requests to
    unqualified domains (#​6744).
  • Support for link-local subnets, i.e. fe80::/16, as client identifiers
    (#​6312).
  • Issues with QUIC and HTTP/3 upstreams on older Linux kernel versions
    (#​6422).
  • YouTube restricted mode is not enforced by HTTPS queries on Firefox.
  • Support for link-local subnets, i.e. fe80::/16, in the access settings
    (#​6192).
  • The ability to apply an invalid configuration for private rDNS, which led to
    server not starting.
  • Ignoring query log for clients with ClientID set (#​5812).
  • Subdomains of in-addr.arpa and ip6.arpa containing zero-length prefix
    incorrectly considered invalid when specified for private rDNS upstream
    servers (#​6854).
  • Unspecified IP addresses aren't checked when using "Fastest IP address" mode
    (#​6875).

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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 Renovate Bot.

@chemical-soup chemical-soup force-pushed the gh-renovate/adguard-adguardhome-0.107.x branch from 47f05a8 to 1f97528 Compare May 27, 2024 13:32
@eiddor
Copy link
Collaborator

eiddor commented May 27, 2024

Running in production

@klutchell
Copy link
Owner

Yeah, weekly seems to be a good cadence for these PRs.

@chemical-soup chemical-soup force-pushed the gh-renovate/adguard-adguardhome-0.107.x branch from 1f97528 to 5f3d2dd Compare June 3, 2024 13:32
@klutchell klutchell merged commit 331cfc7 into main Jun 3, 2024
1 check passed
@klutchell klutchell deleted the gh-renovate/adguard-adguardhome-0.107.x branch June 3, 2024 14:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants