New naming in Jitpack breaks version checks
See original GitHub issueNew naming in Jitpack uses a leading “v”, this breaks “ben manes” gradle version plugin, realted issue is the following: https://github.com/ben-manes/gradle-versions-plugin/issues/277
Plugin now shows:
- com.github.paolorotolo:appintro [v4.2.3 -> 4.1.0]
https://github.com/PaoloRotolo/AppIntro
So it thinks that 4.2.3 is a lower release than 4.1.0 Is it possible to go back to old naming?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
FAQ - JitPack.io
In your build file set the version of your dependency to anyBranch-SNAPSHOT . This is usefull during development but we don't recommend to...
Read more >Cannot detect libraries from jitpack.io · Issue #227 - GitHub
Metadata lists all the existing builds and JitPack checks new GitHub releases in the background. Tried it with this dependency: compile 'com.
Read more >jitpack/jitpack.io - Gitter
I'm try to release my first jar with gradle, where the project is in src folder. It said that first I had to...
Read more >On JitPack's use of git repository name as Maven artifactId
JitPack uses the name of the git repository as the artifactId . ... Renaming the GitHub repository would break existing links to it....
Read more >JitPack - Twitter
Check out JitCI (https://jitci.com) - JitPack's novel CI service with built-in: ✓ Test Tracking ✓ Dependency Checks ✓ Code Coverage ✓ License Reports...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think we should be fine with pushing new tags that copy the old one. From my point of view we should be fine pushing those tags:
And from the upcoming version on let’s use only the name without a
v
Fix merged in master