This PR contains the following updates: | Package | Update | Change | |---|---|---| | [ghcr.io/pi-hole/pihole](https://redirect.github.com/pi-hole/docker-pi-hole) | minor | `7f2dff3` -> `e28e239` | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. Add the preset `:preserveSemverRanges` to your config if you don't want to pin your dependencies. --- ### Release Notes <details> <summary>pi-hole/docker-pi-hole (ghcr.io/pi-hole/pihole)</summary> ### [`v2025.11.0`](https://redirect.github.com/pi-hole/docker-pi-hole/releases/tag/2025.11.0) [Compare Source](https://redirect.github.com/pi-hole/docker-pi-hole/compare/2025.10.3...2025.11.0) Re-release, the `riscv64` part of the image is not currently building and preventing the image from being published for other architectures. I have disabled the `riscv64` build for the time being until I have time to debug what is happening with it. I If you are running this image on `riscv64`, please get in touch via issues if you are willing to help troubleshoot the process! ## Otherwise, nothing specific for Docker, tagging to get an FTL change out: #### What's Changed (FTL v6.3.3) - Fix crash in NTP error handling code by [@​DL6ER](https://redirect.github.com/DL6ER) in [pi-hole/FTL#2684](https://redirect.github.com/pi-hole/FTL/pull/2684) - Add validation for ntp.sync.server by [@​DL6ER](https://redirect.github.com/DL6ER) in [pi-hole/FTL#2667](https://redirect.github.com/pi-hole/FTL/pull/2667) - Be more explicit about required path and query parameters for list manipulation by [@​yubiuser](https://redirect.github.com/yubiuser) in [pi-hole/FTL#2689](https://redirect.github.com/pi-hole/FTL/pull/2689) - Pi-hole FTL v6.3.3 by [@​DL6ER](https://redirect.github.com/DL6ER) in [pi-hole/FTL#2693](https://redirect.github.com/pi-hole/FTL/pull/2693) **Full Changelog**: <https://github.com/pi-hole/FTL/compare/v6.3.2...v6.3.3> </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS44Mi4xMCIsInVwZGF0ZWRJblZlciI6IjQxLjgyLjEwIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbImF1dG9tZXJnZSIsInJlbm92YXRlL2NvbnRhaW5lciIsInR5cGUvbWlub3IiXX0=-->
title
| title |
|---|
| TrueCharts |
Community Helm Chart Catalog
TrueCharts is a catalog of highly optimised Helm Charts. Made for the community, by the community!
All our charts are supposed to work together and be easy to setup using any helm-compatible deployment tool, above all, give the average user more than enough options to tune things to their liking.
Getting started using TrueCharts
Support
Please check our FAQ, manual and Issue tracker There is a significant chance your issue has been reported before!
Still something not working as expected? Contact us! and we'll figure it out together!
Development
Our development process is fully distributed and agile, so every chart-maintainer is free to set their own roadmap and development speed and does not have to comply to a centralised roadmap. This ensures freedom and flexibility for everyone involved and makes sure you, the end user, always has the latest and greatest of every Chart installed.
Getting into creating Charts
For more information check the website: https://truecharts.org
Contact and Support
To contact the TrueCharts project:
-
Create an issue on Github issues
-
Open a Support Ticket
-
Send us an email
Contributors ✨
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!
Licence
Truecharts, is primarily based on the AGPL-v3 license, this ensures almost everyone can use and modify our charts. Licences can vary on a per-Chart basis. This can easily be seen by the presence of a "LICENSE" file in that folder.
An exception to this, has been made for every document inside folders labeled as docs or doc and their subfolders: those folders are not licensed under AGPL-v3 and are considered "all rights reserved". Said content can be modified and changes submitted per PR, in accordance to the github End User License Agreement.
SPDX-License-Identifier: AGPL-3.0