Can we tag the latest changes in this project? #302
Closed
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
Signed-off-by: Marcos Minond <minond.marcos@gmail.com>
Signed-off-by: Marcos Minond <minond.marcos@gmail.com>
|
Closing as duplicate of #311 |
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.
Opening this PR mostly in hopes of getting this project tagged. I'm relying on changes brought in from #291, however the previous tag (
v1.3.5) is a few commits behind and I'd like to be able to pin my kallax dependency to a tag or version wildcard rather than a sha or master's HEAD.Edit: also regenerating the tests with
go generate ./tests/...to get failing build to pass. Looks like the generator is now generating the kallax import statement askallax "gopkg.in/src-d/go-kallax.v1". The diff was causing the build to fail.