-
Notifications
You must be signed in to change notification settings - Fork 1
Update adguard/adguardhome Docker tag to v0.107.71 #7
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
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/adguard-adguardhome-0.x
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
9fe01a4 to
a24f0dd
Compare
a24f0dd to
115db73
Compare
115db73 to
2f07fb7
Compare
2f07fb7 to
e2b5833
Compare
e2b5833 to
f6b958f
Compare
f6b958f to
a05caec
Compare
a05caec to
82fff95
Compare
82fff95 to
1ae2e26
Compare
1ae2e26 to
0c3178c
Compare
0c3178c to
cc67d52
Compare
cc67d52 to
cbb5916
Compare
cbb5916 to
41a77b1
Compare
41a77b1 to
eb3e3b3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.107.56->v0.107.71Release Notes
AdguardTeam/AdGuardHome (adguard/adguardhome)
v0.107.71Compare Source
See also the v0.107.71 GitHub milestone.
Changed
Stale records in optimistic DNS cache now have an upper age limit controlled by
dns.cache_optimistic_max_age. The default value is 12 hours.TTL for stale answers from optimistic DNS cache is now controlled by
dns.cache_optimistic_answer_ttl. The default value is 30 seconds.Configuration changes
In this release, the schema version has changed from 31 to 32.
Added a new string fields
dns.cache_optimistic_answer_ttlanddns.cache_optimistic_max_age.Fixed
v0.107.70Compare Source
See also the v0.107.70 GitHub milestone.
Security
Added
"start_time"in theGET /control/statusresponse.Changed
Stale records in optimistic DNS cache now have an upper age limit of 12 hours.
New blocked services UI.
Fixed
v0.107.69Compare Source
See also the v0.107.69 GitHub milestone.
Changed
Deprecated
Fixed
DHCP settings could not be saved (#8075).
DNS Rewrite edit modal did not populate with the correct values (#8072).
Removed
v0.107.68Compare Source
See also the v0.107.68 GitHub milestone.
Security
Added
New DNS rewrite settings endpoints
GET /control/rewrite/settingsandPUT /control/rewrite/settings/update(#1765). Seeopenapi/openapi.yamlfor details.New fields
"groups"and"group_id"added to the HTTP API (GET /control/blocked_services/all). Seeopenapi/openapi.yamlfor the full description.Changed
POST /control/rewrite/addandPUT /control/rewrite/updatenow accept the optional field "enabled" (#1765). Seeopenapi/openapi.yamlfor details.Configuration changes
In this release, the schema version has changed from 30 to 31.
Added a new boolean field
filtering.rewrites_enabledto globally enable/disable DNS rewrites.Added a new boolean field
enabledfor each entry infiltering.rewritesto toggle individual rewrites.To roll back this change, set
schema_versionback to30.v0.107.67Compare Source
See also the v0.107.67 GitHub milestone.
Added
The HaGeZi's DNS Rebind Protection filter for protecting against DNS rebinding attacks (#102).
Support for configuring the suggested default HTTP port for the installation wizard via the
ADGUARD_HOME_DEFAULT_WEB_PORTenvironment variable (useful for vendors).Changed
Fixed
Excessive configuration file overwrites when visiting the Web UI and a non-empty
languageis set.Lowered the severity of log messages for failed deletion of old filter files (#7964).
v0.107.66Compare Source
See also the v0.107.66 GitHub milestone.
Security
Changed
Our snap package now uses the
core24image as its base.Outgoing HTTP requests now use the
User-AgentheaderAdGuardHome/v0.107.66(wherev0.107.66is the current version) instead ofGo-http-client/1.1(#7979).Fixed
Authentication errors in the Web UI when AdGuard Home is behind a proxy that sets Basic Auth headers (#7987).
The HTTP API
GET /control/profileendpoint failing when no users were configured (#7985).Missing warning on the Encryption Settings page when using a certificate without an IP address.
v0.107.65Compare Source
See also the v0.107.65 GitHub milestone.
Security
Added
A separate checkbox in the Web UI to enable or disable the global DNS response cache without losing the configured cache size.
A new
"cache_enabled"field to the HTTP API (GET /control/dns_infoandPOST /control/dns_config). Seeopenapi/openapi.yamlfor the full description.Changed
Configuration changes
In this release, the schema version has changed from 29 to 30.
Added a new boolean field
dns.cache_enabledto the configuration. This field explicitly controls whether DNS caching is enabled, replacing the previous implicit logic based ondns.cache_size.To roll back this change, set the schema_version back to
29.Fixed
v0.107.64Compare Source
See also the v0.107.64 GitHub milestone.
Security
Fixed
v0.107.63Compare Source
See also the v0.107.63 GitHub milestone.
Security
Fixed
The hostnames of DHCP clients with multiple labels not being recognized.
Status reported by the systemd service implementation in cases of auto-restart after a failed start.
v0.107.62Compare Source
See also the v0.107.62 GitHub milestone.
Security
Fixed
Clients with CIDR identifiers showing zero requests on the Settings → Client settings page (#2945).
Command line option
--updatewhen thedns.serve_plain_dnsconfiguration property was disabled (#7801).DNS cache not working for custom upstream configurations.
Validation process for the DNS-over-TLS, DNS-over-QUIC, and HTTPS ports on the Encryption Settings page.
Searching for persistent clients using an exact match for CIDR in the
POST /clients/searchHTTP API.v0.107.61Compare Source
See also the v0.107.61 GitHub milestone.
Security
Any simultaneous requests that are considered duplicates will now only result in a single request to upstreams, reducing the chance of a cache poisoning attack succeeding. This is controlled by the new configuration object
pending_requests, which has a singleenabledproperty, set totrueby default.NOTE: We thank Xiang Li for reporting this security issue. It's strongly recommended to leave it enabled, otherwise AdGuard Home will be vulnerable to untrusted clients.
v0.107.60Compare Source
See also the v0.107.60 GitHub milestone.
Security
Changed
Dockerfilehas been updated to 3.21 (#7588).Deprecated
Node 20 support, Node 22 will be required in future releases.
NOTE:
npmmay be replaced with a different tool, such aspnpmoryarn, in a future release.Fixed
Filtering for DHCP clients (#7734).
Incorrect label on login page (#7729).
Validation process for the HTTPS port on the Encryption Settings page.
Removed
v0.107.59Compare Source
See also the v0.107.59 GitHub milestone.
Rules with the
clientmodifier not working (#7708).The search form not working in the query log (#7704).
v0.107.58Compare Source
See also the v0.107.58 GitHub milestone.
Security
Added
The ability to check filtering rules for host names using an optional query type and optional ClientID or client IP address (#4036).
Optional
clientandqtypeURL query parameters to theGET /control/check_hostHTTP API.Fixed
Clearing the DNS cache on the DNS settings page now includes both global cache and custom client cache.
Invalid ICMPv6 Router Advertisement messages (#7547).
Disabled button for autofilled login form.
Formatting of elapsed times less than one millisecond.
Changes to global upstream DNS settings not applying to custom client upstream configurations.
The formatting of large numbers in the clients tables on the Client settings page (#7583).
v0.107.57Compare Source
See also the v0.107.57 GitHub milestone.
Security
Added
Changed
Fixed
The hostnames of DHCP clients not being shown in the Top clients table on the dashboard (#7627).
The formatting of large numbers in the upstream table and query log (#7590).
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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.