p#553 Clear velopack's own registry entry in favor of a custom one#5589
Open
akleshchev wants to merge 1 commit intorelease/26.1.1from
Open
p#553 Clear velopack's own registry entry in favor of a custom one#5589akleshchev wants to merge 1 commit intorelease/26.1.1from
akleshchev wants to merge 1 commit intorelease/26.1.1from
Conversation
akleshchev
force-pushed
the
andreyk/p553_registry_cleanup2
branch
2 times, most recently
from
e6b566c to
463a003
Compare
akleshchev
force-pushed
the
andreyk/p553_registry_cleanup2
branch
from
463a003 to
6e77200
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Turns out velopack also has a registry entry (didn't have before?) which was causing issues with our custom one. Velopack doesn't seem to need it for own functionality, so clean it.