mirror of
https://github.com/truecharts/library-charts.git
synced 2026-07-05 01:16:20 -03:00
7433731404
This PR contains the following updates: | Package | Update | Change | |---|---|---| | [tccr.io/tccr/db-wait-mariadb](https://togithub.com/truecharts/containers) | digest | `492a965` -> `62858b8` | | [tccr.io/tccr/db-wait-mongodb](https://togithub.com/truecharts/containers) | digest | `502f70a` -> `9268e23` | | [tccr.io/tccr/db-wait-postgres](https://togithub.com/truecharts/containers) | digest | `a163c78` -> `4e4e5b9` | | [tccr.io/tccr/db-wait-redis](https://togithub.com/truecharts/containers) | digest | `8affa08` -> `e941289` | | [tccr.io/tccr/wget](https://togithub.com/truecharts/containers) | digest | `1764b1b` -> `2c26ff5` | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### 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. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://togithub.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4xMTUuMCIsInVwZGF0ZWRJblZlciI6IjM3LjExNS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9-->
Library Chart
Helm Library Chart for TrueCharts Charts and Apps
Feature addition(s) or enhancements
Please first discuss with us the feature you want to add, especially if it's a large one. This is to ensure we haev an extendable and maintainable implementation!
Keep in mind that both docs and unit tests are required in order to complete/merge the feature addition or enhancement.
Bug fixes
Bug fixes should also be covered by a test case for that scenario. No PRs will be accepted without this.
Contributions
- Any kind of change (feature or bug fix) that alters/adds/removes a key in the values structure have to also be documented
- Additionally, unit tests must be added to cover the change, and if a migration is needed, must be added at the PR description.
Both are a hard requirement.
- Adding dependency handlers in the library chart, would assume that a dependency chart is already implemented and merged in the charts repo.