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

chore(deps): update adguard/adguardhome docker tag to v0.107.48 #1755

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

grey-gorilla
Copy link
Collaborator

@grey-gorilla grey-gorilla commented Mar 20, 2024

This PR contains the following updates:

Package Update Change
adguard/adguardhome (source) patch v0.107.45 -> v0.107.48

Warning

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


Release Notes

AdguardTeam/AdGuardHome (adguard/adguardhome)

v0.107.48

Compare Source

See also the v0.107.48 GitHub milestone.

Fixed
  • Access settings not being applied to encrypted protocols (#​6890)

v0.107.47

Compare Source

See also the v0.107.47 GitHub milestone.

Security
  • Go version has been updated to prevent the possibility of exploiting the Go
    vulnerabilities fixed in Go 1.22.2.
Changed
  • Time Zone Database is now embedded in the binary (#​6758).
  • Failed authentication attempts show the originating IP address in the logs, if
    the request came from a trusted proxy (#​5829).
Deprecated
  • Go 1.22 support. Future versions will require at least Go 1.23 to build.
  • Currently, AdGuard Home uses a best-effort algorithm to fix invalid IDs of
    filtering-rule lists on startup. This feature is deprecated, and invalid IDs
    will cause errors on startup in a future version.
  • Node.JS 16. Future versions will require at least Node.JS 18 to build.
Fixed
  • Resetting DNS upstream mode when applying unrelated settings (#​6851).
  • Symbolic links to the configuration file begin replaced by a copy of the real
    file upon startup on FreeBSD (#​6717).
Removed
  • Go 1.21 support.

v0.107.46

Compare Source

See also the v0.107.46 GitHub milestone.

Added
  • Ability to disable the use of system hosts file information for query
    resolution (#​6610).
  • Ability to define custom directories for storage of query log files and
    statistics (#​5992).
Changed
  • Private rDNS resolution (dns.use_private_ptr_resolvers in YAML
    configuration) now requires a valid "Private reverse DNS servers", when
    enabled (#​6820).

    NOTE: Disabling private rDNS resolution behaves effectively the same as if
    no private reverse DNS servers provided by user and by the OS.

Fixed
  • Statistics for 7 days displayed by day on the dashboard graph (#​6712).
  • Missing "served from cache" label on long DNS server strings (#​6740).
  • Incorrect tracking of the system hosts file's changes (#​6711).

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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@grey-gorilla grey-gorilla force-pushed the renovate/adguard-adguardhome-0.x branch from b824749 to ababa07 Compare April 4, 2024 14:51
@grey-gorilla grey-gorilla changed the title chore(deps): update adguard/adguardhome docker tag to v0.107.46 chore(deps): update adguard/adguardhome docker tag to v0.107.47 Apr 4, 2024
@grey-gorilla grey-gorilla force-pushed the renovate/adguard-adguardhome-0.x branch from ababa07 to 8c54a19 Compare April 5, 2024 15:21
@grey-gorilla grey-gorilla changed the title chore(deps): update adguard/adguardhome docker tag to v0.107.47 chore(deps): update adguard/adguardhome docker tag to v0.107.48 Apr 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant