upgrade Bullseye from 3.6.0 to 4.0.0 #711
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
|
@aaubry any interest in this? |
|
Sure, sorry I was unable to review this earlier. Thanks! |
|
This feature has been released in version 12.1.0. |
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.
I see you're using a few things from the
Bullseye.Internalnamespace—mainlyPaletteandHostExtensions. FYI I'm currently working on making those public in Bullseye 4.1.0. One thing I'd like to confirm before releasing 4.1.0 is that the new API will remove the need for you to use theBullseye.Internalnamespace. But to do that, I think it's best if you've already moved to the Bullseye 4.0.0 API, so we can isolate the changes required for you to move from 4.0.0 to 4.1.0.