Closed jihaisse closed 1 year ago
I did some testing and it looks like a release can have both "links" and "sources" on the same release. I think PUC should also support both. If someone puts in the additional effort to add custom asset links to their release(s), they might want to use those links for updates.
I have refactored the GitLab release asset logic so that the update checker will use "sources" by default, and it will try to use "links" if you call enableReleaseAssets()
. When using "sources", it will choose the first source where format
is zip
.
With those changes, I think this PR is no longer needed. Please try the patched version in the master
branch. If it doesn't work for your use case, please open a new issue.
Thanks for the refactoring, it works great. I'm working on a way to have alpha, beta or other prerelease working with PUC, I will propose something in this way soon, you surely have to rewrite that, but it may be inspiritionnal.
Thanks again for the work
Hello,
Sources links are stored into the sources, not links when build via the pipeline or when a tag is created.
Here is an export of the $release variable from the debugger :
Thanks for the library !