Move to addon v2 blueprint #411
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
…) & fix test errors
NullVoxPopuli
approved these changes
Jun 27, 2024
This was referenced Jun 27, 2024
Merged
Merged
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.
The addon was already a v2 addon, but the addon v2 blueprint was missing, because it was one of the first v2 addon and blueprint was not ready
With this PR we work with v2 addon conventions. Its easier to handle update... in the future.
This is the final step to get ready for next release
Which this change, the drop of node < 18 is not anymore braking, so i think, we can also ship as a minor update all previous changes