Tariffs: fix charges not applied (BC) #14399
Merged
Conversation
This file contains 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
naltatis
approved these changes
Jun 18, 2024
There was a problem hiding this comment.
Config UI ist davon nicht betroffen. Die Eingabe ist bei Tariffs bislang nur via Yaml.
Ich hab gerade noch mal das Doku Projekt durchgeschaut. Da haben wir costs nicht explizit erwähnt. Die Änderungen pro Tarif ergeben sich ja aus den yaml. Diese werden automatisch beim nächsten Release ersetzt und deployt.
|
Sollte man das nicht für die Release Notes als "BC" markieren. |
andig
changed the title
|
Ja, danke 🙏 |
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.
Replaces #14398
@naltatis muss dafür jetzt bei Config-UI etwas angepasst werden? Leider ist dieser Change breaking, ich habe allerdings die Hoffnung, dass er vielleicht noch nicht allzuviel kaputt macht???