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

Update Docker image pihole/pihole to v2024.07.0 #310

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 7, 2024

This PR contains the following updates:

Package Update Change
pihole/pihole major 2023.11.0 -> 2024.07.0

Release Notes

pi-hole/docker-pi-hole (pihole/pihole)

v2024.07.0

Compare Source

Nothing Docker-specific, retagging to include which includes a hotfix for a reported vulnerability

What's Changed (Core v5.18.3)

Full Changelog: pi-hole/pi-hole@v5.18.2...v5.18.3

v2024.06.0: (The "I can't believe it wasn't working on 32-bit machines for the past year" edition)

Compare Source

Fixes compatibility with 32-bit (i386/x86/whatever you want to call it) architecture by ensuring the correct s6-overlay binaries are downloaded. No other changes for other architectures.

What's Changed

Full Changelog: pi-hole/docker-pi-hole@2024.05.0...2024.06.0

v2024.05.0

Compare Source

New tag to include FTL v5.25.2. No docker-specific changes

What's Changed (FTL v5.25.2)

Full Changelog: pi-hole/FTL@v5.25.1...v5.25.2

v2024.03.2

Compare Source

New tag to include core v5.18.2

What's Changed (Core v5.18.2)

New Contributors

Full Changelog: pi-hole/pi-hole@v5.18.1...v5.18.2

v2024.03.1

Compare Source

New tag to include core hotfix 5.18.1

What's Changed Core v5.18.1

Full Changelog: pi-hole/pi-hole@v5.18...v5.18.1

v2024.03.0

Compare Source

Nothing Docker-specific this release. Tagging a new image to include Pi-hole Core v5.18's vulnerability fix

What’s Changed Core v5.18

  • Drop Fedora 36 and add Fedora 39 to the test suite by @​yubiuser in #​5568
  • [Vulnerability Fix] Only use local files (file://) when they have explicit permissions a+r by @​DL6ER 9dd138b

Full Changelog: v5.17.3...v5.18

v2024.02.2

Compare Source

Jumped the gun a little with the last tag - didn't realise there were changes ready to go! Should fix: https://github.com/pi-hole/docker-pi-hole/issues/1543

What's Changed

New Contributors

Full Changelog: pi-hole/docker-pi-hole@2024.02.0...2024.02.2

v2024.02.1

Compare Source

Nothing Docker-specific this time around, tagging to include FTL v5.25.1

What's Changed (FTL)

Full Changelog: pi-hole/FTL@v5.25...v5.25.1

v2024.02.0

Compare Source

Nothing Docker-specific this time around.

Tagging to include FTL v5.25

See our recent blog post for details concerning this release.

What's Changed (FTL)

Full Changelog: pi-hole/FTL@v5.24...v5.25

v2024.01.0

Compare Source

Nothing docker specific this time around.

What's Changed (FTL v5.24)

Full Changelog: pi-hole/FTL@v5.23...v5.24

What's Changed (Core v5.17.3)

Full Changelog: pi-hole/pi-hole@v5.17.2...v5.17.3


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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title Update Docker image pihole/pihole to v2024.01.0 Update Docker image pihole/pihole to v2024.02.0 Feb 14, 2024
@renovate renovate bot force-pushed the renovate/pihole-pihole-2024.x branch from c9f5fa5 to 600fce1 Compare February 14, 2024 21:29
@renovate renovate bot changed the title Update Docker image pihole/pihole to v2024.02.0 Update Docker image pihole/pihole to v2024.02.2 Feb 26, 2024
@renovate renovate bot force-pushed the renovate/pihole-pihole-2024.x branch from 600fce1 to 6dc5e75 Compare February 26, 2024 21:56
@renovate renovate bot force-pushed the renovate/pihole-pihole-2024.x branch from 6dc5e75 to b53ea4a Compare March 27, 2024 20:28
@renovate renovate bot changed the title Update Docker image pihole/pihole to v2024.02.2 Update Docker image pihole/pihole to v2024.03.1 Mar 27, 2024
@renovate renovate bot force-pushed the renovate/pihole-pihole-2024.x branch from b53ea4a to ddd5676 Compare March 31, 2024 22:12
@renovate renovate bot changed the title Update Docker image pihole/pihole to v2024.03.1 Update Docker image pihole/pihole to v2024.03.2 Mar 31, 2024
@renovate renovate bot changed the title Update Docker image pihole/pihole to v2024.03.2 Update Docker image pihole/pihole to v2024.05.0 May 8, 2024
@renovate renovate bot force-pushed the renovate/pihole-pihole-2024.x branch from ddd5676 to fad9968 Compare May 8, 2024 22:10
@renovate renovate bot changed the title Update Docker image pihole/pihole to v2024.05.0 Update Docker image pihole/pihole to v2024.06.0 Jun 16, 2024
@renovate renovate bot force-pushed the renovate/pihole-pihole-2024.x branch from fad9968 to ac01a87 Compare June 16, 2024 21:08
| datasource | package       | from      | to        |
| ---------- | ------------- | --------- | --------- |
| docker     | pihole/pihole | 2023.11.0 | 2024.07.0 |
@renovate renovate bot force-pushed the renovate/pihole-pihole-2024.x branch from ac01a87 to 1338d72 Compare July 5, 2024 23:01
@renovate renovate bot changed the title Update Docker image pihole/pihole to v2024.06.0 Update Docker image pihole/pihole to v2024.07.0 Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants