Trez/rinoa-docker
4
0
Fork 0
Code Issues 1 Pull Requests 9 Actions 1 Activity

🔧 Renovate: Update (patch) adguard/adguardhome Docker tag to v0.107.71 #1483

Merged
renovate-bot merged 1 commits from renovate/docker-compose-adguard-adguardhome-v0-107-71 into main 2025-12-14 01:55:22 -05:00
Conversation 0 Commits 1 Files Changed 1
+1 -1
renovate-bot commented 2025-12-14 01:55:14 -05:00
Member
Copy Link
Copy Source

This PR contains the following updates:

Package Update Change
adguard/adguardhome (source) patch v0.107.70 -> v0.107.71

⚠️ Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

⚡ Renovate Update Info

  • Update Type: patch

  • Automerge: 🛑 This update requires manual approval

Release Notes

AdguardTeam/AdGuardHome (adguard/adguardhome)

v0.107.71

Compare 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_ttl and dns.cache_optimistic_max_age.

    # BEFORE:
'dns':
  'cache_enabled': true
  'cache_optimistic': true
  # …

# AFTER:
'dns':
  'cache_enabled': true
  'cache_optimistic': true
  'cache_optimistic_answer_ttl': '30s'
  'cache_optimistic_max_age': '12h'
  # …
  ```

To roll back this change, set the `schema_version` back to `31`.
Fixed
  • Optimistic DNS cache not working (#​8148).

Configuration

📅 Schedule: Branch creation - At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday ( * 0-4,22-23 * * 1-5 ), Only on Sunday and Saturday ( * * * * 0,6 ) (UTC), 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 | Update | Change | |---|---|---| | [adguard/adguardhome](https://adguard.com/en/adguard-home/overview.html) ([source](https://github.com/AdguardTeam/AdGuardHome)) | patch | `v0.107.70` -> `v0.107.71` | --- > ⚠️ **Warning** > > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. ### ⚡ Renovate Update Info - **Update Type:** patch - **Automerge:** 🛑 This update requires manual approval --- ### Release Notes <details> <summary>AdguardTeam/AdGuardHome (adguard/adguardhome)</summary> ### [`v0.107.71`](https://github.com/AdguardTeam/AdGuardHome/blob/HEAD/CHANGELOG.md#v010771---2025-12-08) [Compare Source](https://github.com/AdguardTeam/AdGuardHome/compare/v0.107.70...v0.107.71) See also the [v0.107.71 GitHub milestone][ms-v0.107.71]. ##### 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_ttl` and `dns.cache_optimistic_max_age`. ````yaml # BEFORE: 'dns': 'cache_enabled': true 'cache_optimistic': true # … # AFTER: 'dns': 'cache_enabled': true 'cache_optimistic': true 'cache_optimistic_answer_ttl': '30s' 'cache_optimistic_max_age': '12h' # … ``` To roll back this change, set the `schema_version` back to `31`. ```` ##### Fixed - Optimistic DNS cache not working ([#&#8203;8148]). [#&#8203;8148]: https://github.com/AdguardTeam/AdGuardHome/issues/8148 [ms-v0.107.71]: https://github.com/AdguardTeam/AdGuardHome/milestone/106?closed=1 </details> --- ### Configuration 📅 **Schedule**: Branch creation - At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday ( * 0-4,22-23 * * 1-5 ), Only on Sunday and Saturday ( * * * * 0,6 ) (UTC), 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:eyJjcmVhdGVkSW5WZXIiOiI0Mi4yNi4xMSIsInVwZGF0ZWRJblZlciI6IjQyLjI2LjExIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZSJdfQ==-->
renovate-bot added the dependenciesrenovate labels 2025-12-14 01:55:14 -05:00
renovate-bot added 1 commit 2025-12-14 01:55:16 -05:00
🔧 Renovate: Update (patch) adguard/adguardhome Docker tag to v0.107.71
Renovate Image Tag Deployment / Renovate PR Deployment (pull_request) Failing after 3m46s
Details
d09fa41359
renovate-bot scheduled this pull request to auto merge when all checks succeed 2025-12-14 01:55:19 -05:00
renovate-bot merged commit 7264ed44a9 into main 2025-12-14 01:55:22 -05:00
renovate-bot deleted branch renovate/docker-compose-adguard-adguardhome-v0-107-71 2025-12-14 01:55:25 -05:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
dependencies
docker-compose
manual
renovate
No Label dependencies renovate
Milestone
No items
No Milestone
Assignees
Clear assignees
gitea-sonarqube-bot renovate-bot root Trez.One
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Trez/rinoa-docker#1483
Delete Branch "renovate/docker-compose-adguard-adguardhome-v0-107-71"

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?