Config UI: remove obsolete migrations (BC) #19417
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
changed the title
The db schema change was not introduced on Jan 2025 (as I thought) with the new loadpoint config UI. It's already in master since Aug 2024 0.129.0. Therefore it's totally fine for me to require users of this old version to do a two step migration (0.129.0 > 0.200.9 > latest) in case they won't to maintain their previous config ui configuration. |
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.
TODO
detailsFromMapmagic is still necessaryBreaking Change (experimental)
If you're directly migrating from an evcc version <= v0.129.0 (Jul, 2024) and have used Config UI, you'll use your UI-configured meters and vehicles and have to configure them again. Alternatively you can do a two step. First update to 0.200.9, start evcc once and update to latest.