Make v2 schema the default #343
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
This was referenced Aug 21, 2025
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.
Support for a tree structure multiple branches in any level of a stack got added in
v0.12.0. As part of this there was a new v2 schema introduced with a command to migrate from v1 to v2. This allowed me to add all the support in stages. This is all done now and I've been using full tree support for some time and am ready to make it the only structure supported.The first PR of this is to make the v2 schema the default when this tool is used for the first time. There will be some updates later to force migration from v1 to v2 (behind the scenes probably) and then to remove the v1 schema in some areas altogether.