You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Relying on GitHub releases would be a very specific feature to GitHub, we already support the far more generic concept of Git tags, which you have to use when you create a release on GitHub iirc. I'm not sure what adding support for this would achieve that our support for git tags doesn't already?
Some projects don't distribute their assets in the git repository, instead, they rely on GitHub releases take Iosevka as an example. The repository only contains the source code and the releases page contains all the assets.
Ah, yeah, I guess that somewhat makes sense, though the example you've given wouldn't be supported still as cdnjs does not host ZIP files -- I guess there could be some packages that have their distributable files directly exposed in the assets of a release but not anywhere else (NPM package, repo, etc.)
I think before we invest any time into working to support this, I'd like to better gauge the interest and need for it -- what packages are there out there that cdnjs should have currently but can't because they only release their distributable assets via GitHub release assets?
I would love to see support for Github releases as an auto-update source. We can use Github API to fetch a list of releases along with their assets https://docs.github.com/en/rest/reference/repos#releases
The text was updated successfully, but these errors were encountered: