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
Is your feature request related to a problem? Please describe.
While using Gitea, packages and binaries are currently just being uploaded as assets to releases.
But Gitea now provides its own package registries. In the current development version, there is e.g. a registry for Debian, RPM, Alpine and many others.
Instead of uploading it as a Asset, we could upload it directly to the Gitea Package Registry which would make distribution for the users easier.
In my use case, I have multiple packages which I want to distribute to multiple servers via the Gitea Package Registry. I can already do that but would need to write my own code for adding it to the Gitea Registry.
Describe the solution you'd like
We already have the Gitea Token, Repository and Organisation or User as Env Vars in this project, for supporting the Gitea Package registry, just a few more API calls would have to be added.
The current alternative would be that every user creates his own implementation. My plan would be to make the API-Call myself in the Pipeline and upload the package there.
Search
I did search for other open and closed issues before opening this
I think gitea/go-sdk should support the uploading package sdk first, otherwise, there is no way for goreleaser to support this feature. Please let me know if I'm missing something or if there is another workaround.
Is your feature request related to a problem? Please describe.
While using Gitea, packages and binaries are currently just being uploaded as assets to releases.
But Gitea now provides its own package registries. In the current development version, there is e.g. a registry for Debian, RPM, Alpine and many others.
Instead of uploading it as a Asset, we could upload it directly to the Gitea Package Registry which would make distribution for the users easier.
In my use case, I have multiple packages which I want to distribute to multiple servers via the Gitea Package Registry. I can already do that but would need to write my own code for adding it to the Gitea Registry.
Describe the solution you'd like
We already have the Gitea Token, Repository and Organisation or User as Env Vars in this project, for supporting the Gitea Package registry, just a few more API calls would have to be added.
E.g. to publish a package:
(See: https://docs.gitea.com/next/usage/packages/packages/debian)
Describe alternatives you've considered
The current alternative would be that every user creates his own implementation. My plan would be to make the API-Call myself in the Pipeline and upload the package there.
Search
Supporter
Code of Conduct
Additional context
No response
The text was updated successfully, but these errors were encountered: