-
Notifications
You must be signed in to change notification settings - Fork 355
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release on GitHub #193
Release on GitHub #193
Conversation
4a20569
to
84800ff
Compare
84800ff
to
0c3a944
Compare
Is there a reason this is not handled by jitpack? Seems like duplicate generation of aar files no? |
Jitpack has currently only Android aar , for PC the *.jar files are now on github, it's a kind of replace of directory |
Is that true? The doc link I sent seems to indicate you can also generate JAR files and points to this file as an example. It'd be nice if they were all in the same place if possible, but I agree that github releases make more sense than a releases folder. |
0c3a944
to
61b189d
Compare
Now https://jitpack.io/#ytai/ioio/6.0.0.beta6 has |
61b189d
to
6abf951
Compare
Nice job! One issue I see with these still though is there doesn't appear to be any release notes, or anything to differentiate between releases. Is there a way to add release notes to these detailing what has been updated? It would likely take a bit more work to write these nicely for all beta releases, but at the very least, could we maybe just bundle all the master branch commit messages between the release and the previous release? For example I don't know if the newer releases are based on the AppCompat libraries or not without downloading the whole set and testing whether it breaks my project or not. |
Never mind. I had no idea github could do a diff on them directly. Not need for release notes if that is the case. |
This will upload libaries artifacts to github release like
https://github.com/hannesa2/ioio/releases/tag/6.0.0-beta4.r20