TrueCharts Bot
dbd68aaff7
This PR contains the following updates: | Package | Update | Change | |---|---|---| | [docker.io/2fauth/2fauth](https://redirect.github.com/Bubka/2FAuth) | major | `0b2e2ea` → `4209283` | --- > [!WARNING] > Some dependencies could not be looked up. Check the [Dependency Dashboard](../issues/18710) for more information. Add the preset `:preserveSemverRanges` to your config if you don't want to pin your dependencies. --- ### Release Notes <details> <summary>Bubka/2FAuth (docker.io/2fauth/2fauth)</summary> ### [`v7.0.1`](https://redirect.github.com/Bubka/2FAuth/blob/HEAD/changelog.md#701---2026-06-09) [Compare Source](https://redirect.github.com/Bubka/2FAuth/compare/v7.0.0...v7.0.1) ##### Fixed - [issue #​548](https://redirect.github.com/Bubka/2FAuth/issues/548) Sharing actions only available in “Show Password: After a Click/Tab” view, not obvious to users ### [`v7.0.0`](https://redirect.github.com/Bubka/2FAuth/blob/HEAD/changelog.md#700---2026-06-08) [Compare Source](https://redirect.github.com/Bubka/2FAuth/compare/v6.1.3...v7.0.0) Account sharing has finally arrived in 2FAuth!\ First mentioned in February 2024, I believe this is the most anticipated feature since the beginning of 2FAuth's development. First, a quick reminder: The purpose of 2FA is to provide a second piece of evidence to prove your identity during an authentication process. That means the secret which allow to generate this short-lived piece of evidence, the One-Time Password, must be kept in a safe place and it should not be disclosed. This has guided the development of 2FAuth up to now and has also influenced the way the sharing feature has been designed: The shared resource should be the ability to generate OTPs, not the secret itself. In practice, sharing a 2FA account in 2FAuth does not grant the recipient full access to the account. While the recipient can view the account and generate OTPs, they cannot access the secret. Therefore, no editing, exporting, or displaying of QR codes is possible; these functions remain exclusive to the owner. From a UI perspective, I did my best to make it clear what is shared, with whom and under which conditions, while ensuring a seamless fit with the existing design — even on mobile — without disrupting the user experience. I hope you find this intregration efficient and convenient. This release also introduces the ability to transfer ownership of a 2FA account. This feature should provide flexibility for team-based usage, especially when responsibilities change or access needs to be transferred to another person. Please note that ownership transfer is only available when sharing is enabled. To complete the picture, OTP generation now comes with a log that is directly available in the web application. This audit trail makes it easy to review usage and keep track of who generated a code and when, without recording the code itself. 2FA Sharing is disabled by default. You can activate it from the Admin Panel. If you'd like to learn more, please consult the [2FA Sharing documentation](https://docs.2fauth.app/usage/2fa-sharing/). ##### Added - 2FA sharing - 2FA ownership transfer - OTP generation log - Expiration date of OAuth tokens in User Settings ([#​536](https://redirect.github.com/Bubka/2FAuth/issues/536)). ##### Changed - Dependency on the `APP_URL` environment variable has been reduced. It is now possible to access the web app using a URL other than the one set in `APP_URL`. Typically, this would be an internal URL, such as a local IP address. **Important**: Some features still rely on `APP_URL` to work as expected. These include SSO (during redirections) and WebAuthn authentication. - Minor UI adjustments ##### Fixed - [issue #​538](https://redirect.github.com/Bubka/2FAuth/issues/538) Search field gets focus when trying to select an account in Manage mode using keyboard - [issue #​545](https://redirect.github.com/Bubka/2FAuth/issues/545) Case sensitivity in e-mail/uid-string during SSO authentication - [issue #​546](https://redirect.github.com/Bubka/2FAuth/issues/546) Unencoded # in otpauth URI breaks decoding ##### API \[1.10.0] - New `is_borrowed`, `shared_by`, `is_shared` and `is_shared_with_all` properties in `2FAccount` resource description. See GET `/api/v1/twofaccounts/{id}` ([doc](https://docs.2fauth.app/resources/rapidoc.html#get-/api/v1/twofaccounts/-id-)) and GET `/api/v1/twofaccounts` ([doc](https://docs.2fauth.app/resources/rapidoc.html#get-/api/v1/twofaccounts)). - `/api/v1/twofaccounts/{id}/owner` PATCH path added ([doc](https://docs.2fauth.app/resources/rapidoc.html#patch-/api/v1/twofaccounts/-id-/owner)). - `/api/v1/twofaccounts/{id}/recipients` GET path added ([doc](https://docs.2fauth.app/resources/rapidoc.html#get-/api/v1/twofaccounts/-id-/recipients)). - `/api/v1/twofaccounts/{id}/shares` GET, POST, DELETE paths added ([doc](https://docs.2fauth.app/resources/rapidoc.html#get-/api/v1/twofaccounts/-id-/shares)). - `/api/v1/twofaccounts/{id}/shares/all` POST path added ([doc](https://docs.2fauth.app/resources/rapidoc.html#post-/api/v1/twofaccounts/-id-/shares/all)). - `/api/v1/twofaccounts/{id}/shares/{userid}` DELETE path added ([doc](https://docs.2fauth.app/resources/rapidoc.html#delete-/api/v1/twofaccounts/-id-/shares/-userid-)). - Documentation for `/api/v1/features` GET path added ([doc](https://docs.2fauth.app/resources/rapidoc.html#get-/api/v1/features)). </details> --- ### Configuration 📅 **Schedule**: (UTC) - 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. --- - [ ] <!-- 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:eyJjcmVhdGVkSW5WZXIiOiI0My4xMzAuMSIsInVwZGF0ZWRJblZlciI6IjQzLjEzMC4xIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbImFwcC90d29mYXV0aCIsInJlbm92YXRlL2NvbnRhaW5lciIsInR5cGUvbWFqb3IiXX0=-->
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):
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?v=4?s=100)
![allcontributors[bot]](https://avatars.githubusercontent.com/in/23186?v=4?s=100)
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4?s=100)
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
