-
-
Notifications
You must be signed in to change notification settings - Fork 236
Be more explicit about required path and query parameters for list manipulation #2689
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
β¦nipulation Signed-off-by: yubiuser <[email protected]>
DL6ER
approved these changes
Nov 1, 2025
truecharts-admin
added a commit
to trueforge-org/truecharts
that referenced
this pull request
Nov 5, 2025
#41431) 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**: <pi-hole/FTL@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=-->
github-actions bot
pushed a commit
to bigbeartechworld/big-bear-universal-apps
that referenced
this pull request
Nov 8, 2025
This PR contains the following updates: | Package | Update | Change | |---|---|---| | [jacklul/pihole](https://redirect.github.com/pi-hole/docker-pi-hole) | minor | `2025.10.3` -> `2025.11.0` | --- ### Release Notes <details> <summary>pi-hole/docker-pi-hole (jacklul/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**: <pi-hole/FTL@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 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 was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/bigbeartechworld/big-bear-universal-apps). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNTkuNCIsInVwZGF0ZWRJblZlciI6IjQxLjE1OS40IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZSJdfQ==-->
github-actions bot
pushed a commit
to bigbeartechworld/big-bear-universal-apps
that referenced
this pull request
Nov 9, 2025
This PR contains the following updates: | Package | Update | Change | |---|---|---| | [pihole/pihole](https://redirect.github.com/pi-hole/docker-pi-hole) | minor | `2025.10.3` -> `2025.11.0` | --- ### Release Notes <details> <summary>pi-hole/docker-pi-hole (pihole/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**: <pi-hole/FTL@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 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 was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/bigbeartechworld/big-bear-universal-apps). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNTkuNCIsInVwZGF0ZWRJblZlciI6IjQxLjE1OS40IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZSJdfQ==-->
github-actions bot
pushed a commit
to bigbeartechworld/big-bear-universal-apps
that referenced
this pull request
Nov 14, 2025
β¦ag to v2025.11.0 This PR contains the following updates: | Package | Update | Change | |---|---|---| | [bigbeartechworld/big-bear-pihole-unbound](https://redirect.github.com/pi-hole/docker-pi-hole) | minor | `2025.08.0` -> `2025.11.0` | --- ### Release Notes <details> <summary>pi-hole/docker-pi-hole (bigbeartechworld/big-bear-pihole-unbound)</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.08.0...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**: <pi-hole/FTL@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 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 was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/bigbeartechworld/big-bear-universal-apps). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNzMuMSIsInVwZGF0ZWRJblZlciI6IjQxLjE3My4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZSJdfQ==-->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR aim to accomplish?:
Follow-up on #2530 to be even more explicit about the requirement to add
{listtype}forPUTandDELETErequests.Fixes #2685
By submitting this pull request, I confirm the following:
git rebase)