rock
rock copied to clipboard
pkg
Create semantic version tags for your Go packages, search and discover new packages
When existing tags were not sorted, next tag was generated incorrectly. The program would assume minor version from a smaller major version in some cases. For example, if current largest...
I have old version 1.0.2 and current 1.1.0 Command `rock tag -p` produce wrong version v1.1.3 instead v1.1.1 ``` Existing Tags: v1.0.1 v1.0.0 v1.1.0 v1.0.2 Creating v1.1.3 Tagged and pushed...
This should not be a duplicate of #3 since I am not using packed tags in http://github.com/hhrutter/pdfcpu but > rock tags returns an incomplete tag list compared to > git...
"rock search" keeps returning the following for me regardless of any supplied arguments.: > Unmarshaling response.: invalid character 'B' after top-level value I am on go1.9/linux64 but the same happens...
Inspect current against previously tagged version, use the AST to determine if breaking changes, new features, or no features were added. Suggest appropriate release tag bump