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
I'm (one of) the package maintainer for the protonmail-bridge Arch Linux package.
Our packaging tooling/workflow relies on a "version checker" tool to generate alerts on new upstream releases and it's a bit difficult for that tool to filter out GitHub releases tagged as "pre-release" (it's actually possible but the way it is done is a bit tedious for us integration wise).
As such, using a specific tag suffix for pre-releases (e.g. -dev, -beta, -rc,... like gitea does for instance) would be ideal for us as it would give us a simple pattern to filter out on our side (instead of verifying if a new release is tagged as "pre-release" or not on the GitHub side), streamlining our "version checking" process for our protonmail-bridge package.
Would that be a possibility on your side?
By the way, I'm sorry if this is the wrong place to ask.
Thanks in advance :)
The text was updated successfully, but these errors were encountered:
Hi,
I'm (one of) the package maintainer for the protonmail-bridge Arch Linux package.
Our packaging tooling/workflow relies on a "version checker" tool to generate alerts on new upstream releases and it's a bit difficult for that tool to filter out GitHub releases tagged as "pre-release" (it's actually possible but the way it is done is a bit tedious for us integration wise).
As such, using a specific tag suffix for pre-releases (e.g. -dev, -beta, -rc,... like gitea does for instance) would be ideal for us as it would give us a simple pattern to filter out on our side (instead of verifying if a new release is tagged as "pre-release" or not on the GitHub side), streamlining our "version checking" process for our protonmail-bridge package.
Would that be a possibility on your side?
By the way, I'm sorry if this is the wrong place to ask.
Thanks in advance :)
The text was updated successfully, but these errors were encountered: