Created attachment 264161 [details] Update from 0.107.66 to 0.107.67 This patch updates www/adguardhome from 0.107.66 to 0.107.67 CHANGELOG 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_PORT environment variable (useful for vendors). Changed: - Optimized matching of filtering rules. Fixed: - Excessive configuration file overwrites when visiting the Web UI and a non-empty language is set. - Lowered the severity of log messages for failed deletion of old filter files (#7964). Full changelog is available on official GitHub repository https://github.com/AdguardTeam/AdGuardHome/releases/tag/v0.107.67 It works fine on 14.3-RELEASE amd64.
Created attachment 264331 [details] Update from 0.107.66 to 0.107.67 ^Triage: rebase patch.
Created attachment 264812 [details] Update from 0.107.66 to 0.107.68
A new version has been released before the approval of this patch. I propose this patch to update this port www/adguardhome from 0.107.66_2 to 0.107.68. CHANGELOG Let's get “the usual” out of the way: we’ve made some security updates, as we always do, and even managed to make do without any bug fixes this time, for better or for worse. But let’s focus on the main course: new option to enable and disable DNS rewrite rules. This was one of the earlier feature requests, and we are happy to finally deliver. You can enable and disable DNS rewrite rules all at once or do so on an individual rewrite basis — both by editing YAML files or via UI. Added - New DNS rewrite settings endpoints GET /control/rewrite/settings and PUT /control/rewrite/settings/update (#1765). See openapi/openapi.yaml for details. New fields "groups" and "group_id" added to the HTTP API (GET /control/blocked_services/all). See openapi/openapi.yaml for the full description. Changed - POST /control/rewrite/add and PUT /control/rewrite/update now accept the optional field "enabled" (#1765). See openapi/openapi.yaml for details. Configuration changes In this release, the schema version has changed from 30 to 31. - Added a new boolean field filtering.rewrites_enabled to globally enable/disable DNS rewrites. - Added a new boolean field enabled for each entry in filtering.rewrites to toggle individual rewrites.
This patch works fine on 14.3-RELEASE amd64. I cannot mark as obsolete Mark's patch on my side.
Full changelog is available on official Github repository https://github.com/AdguardTeam/AdGuardHome/releases/tag/v0.107.68
A new version has been released before the approval of this patch. I propose this patch to update this port www/adguardhome from 0.107.66_2 to 0.107.69. I added node24 as build dependency as required in this new version. CHANGELOG AdGuard Home v0.107.69 is here — just a quick pit stop to fix two pesky bugs that tried to sneak past us. No new features this time, but everything should now run a bit smoother (and those bugs have been shown the door). Full changelog: https://github.com/AdguardTeam/AdGuardHome/releases/tag/v0.107.69 Changed: - Node.js 24 is now used to build the frontend. Deprecated: - Node.js 20 and 22 support. Fixed: - DHCP settings could not be saved (#8075). - DNS Rewrite edit modal did not populate with the correct values (#8072). Removed: - The outdated querylog anonymization script. --- This patch works fine on 14.3-RELEASE amd64. I cannot mark as obsolete Mark's patch on my side.
Created attachment 265034 [details] Update from 0.107.66 to 0.107.69
Is anyone tested this patch to confirm it works fine?
I close it because it is irrelevant now. The maintainer yuri@ updated the port himself. Thank you yuri@