vendor: update complete version to v1.1 #3646
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
|
@posener Yes, we changed the format. You can run Also |
|
Also, could you provide some details on what improvements/changes we can expect to see with the updated version, so that we can test for it and update Consul's changelog appropriately? |
Update posener/complete to revision=v1.1. Leave only once occurrence of posener/complete in vendor, there was an occurrence for each package individualy. The formatting of vendor/vendor.json has changed after using the command "govendor fetch github.com/posener/complete@=v1.1"
posener
force-pushed
the
update-complete
branch
from
2ea7540 to
feea8d6
Compare
|
Hi @preetapan |
|
Thanks! |
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.
Update posener/complete to revision=v1.1.
Changes in bash completion:
I left only one occurrence of posener/complete in the vendor/vendor.json, there was an occurrence for
each package individually.