remoll/k3s-infra
0
0
Fork 0
Code Issues 1 Pull Requests 10 Packages Projects Releases Wiki Activity

Update adguard/adguardhome Docker tag to v0.107.65 #573

Merged
renovate merged 1 commits from renovate/adguard-adguardhome-0.x into main 2025-09-03 12:02:29 +00:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
renovate commented 2025-09-03 12:02:25 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Type Update Change
adguard/adguardhome (source) Kustomization patch v0.107.64 -> v0.107.65

Release Notes

AdguardTeam/AdGuardHome (adguard/adguardhome)

v0.107.65

Compare Source

See also the v0.107.65 GitHub milestone.

Security
  • Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.24.6.
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_info and POST /control/dns_config). See openapi/openapi.yaml for 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_enabled to the configuration. This field explicitly controls whether DNS caching is enabled, replacing the previous implicit logic based on dns.cache_size.

BEFORE:

'dns':

…

    'cache_size': 123456

AFTER:

'dns':

…

    'cache_enabled': true
    'cache_size': 123456
```

To roll back this change, set the schema_version back to `29`.
Fixed
  • Disabled state of Top clients action button in web UI (#​7923).

Configuration

📅 Schedule: 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 Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [adguard/adguardhome](https://adguard.com/en/adguard-home/overview.html) ([source](https://github.com/AdguardTeam/AdGuardHome)) | Kustomization | patch | `v0.107.64` -> `v0.107.65` | --- ### Release Notes <details> <summary>AdguardTeam/AdGuardHome (adguard/adguardhome)</summary> ### [`v0.107.65`](https://github.com/AdguardTeam/AdGuardHome/blob/HEAD/CHANGELOG.md#v010765---2025-08-20) [Compare Source](https://github.com/AdguardTeam/AdGuardHome/compare/v0.107.64...v0.107.65) See also the [v0.107.65 GitHub milestone][ms-v0.107.65]. ##### Security - Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in [1.24.6][go-1.24.6]. ##### 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_info` and `POST /control/dns_config`). See `openapi/openapi.yaml` for 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_enabled` to the configuration. This field explicitly controls whether DNS caching is enabled, replacing the previous implicit logic based on `dns.cache_size`. ```yaml ``` ### BEFORE: ``` 'dns': ``` ### … ``` 'cache_size': 123456 ``` ### AFTER: ``` 'dns': ``` ### … ```` 'cache_enabled': true 'cache_size': 123456 ``` To roll back this change, set the schema_version back to `29`. ```` ##### Fixed - Disabled state of *Top clients* action button in web UI ([#&#8203;7923]). [#&#8203;7923]: https://github.com/AdguardTeam/AdGuardHome/issues/7923 [go-1.24.6]: https://groups.google.com/g/golang-announce/c/x5MKroML2yM [ms-v0.107.65]: https://github.com/AdguardTeam/AdGuardHome/milestone/100?closed=1 </details> --- ### Configuration 📅 **Schedule**: 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS45NC4wIiwidXBkYXRlZEluVmVyIjoiNDEuOTQuMCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->
renovate added 1 commit 2025-09-03 12:02:26 +00:00
Update adguard/adguardhome Docker tag to v0.107.65 a2cff0bf55
renovate scheduled this pull request to auto merge when all checks succeed 2025-09-03 12:02:27 +00:00
renovate merged commit 3aa05f3e30 into main 2025-09-03 12:02:29 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
renovate remoll
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: remoll/k3s-infra#573
No description provided.
Delete Branch "renovate/adguard-adguardhome-0.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?