Proposal: gitea-releases #20740
Replies: 4 comments 3 replies
-
Not sure if I did something wrong with the proposal as I see down votes by maintainers. Was this discussed and maybe rejected somewhere else and I did not find it? Would it be too complex to maintain? I appreciate any feedback so that I can understand the reactions and adjust the proposal if something is missing. |
Beta Was this translation helpful? Give feedback.
-
this datasource should be modeled like the Gitlab releases. so auth is already handled by lower http layer. for it to work we only need the datasource, wich does the JSON request via http layer and transforms the results to renovate releases. should be easy to implement. |
Beta Was this translation helpful? Give feedback.
-
Here is the |
Beta Was this translation helpful? Give feedback.
-
Type of discussion.
I'm proposing an idea
Tell us more.
👋 Hi. First of all: Renovate is awesome. Thanks for maintaining this project.
I would like to propose a new datasource:
gitea-releases
. Similar to thegithub-releases
it would be great to extract details from releases hosted on Gitea instances.Configuration
Since Gitea is not one single instance but many self-hosted ones, the host should be part of the dependency name. A better alternative might be the "registry" concept from Docker.
API
There are only small differences between Gitea and GitHub. It should be straight forward.
Authentication
I am not sure if access tokens are required for it to work in an initial state. Gitea doesn't have built-in rate limits, afaik.
For an actual authentication the concept from Docker/NPM registries with "Host -> Token" mapping could work.
Beta Was this translation helpful? Give feedback.
All reactions