-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement the ability to sort different versioning schemes #1540
Comments
I thought I already have issue for this, it seems that I don't have yet. So for now the only option is to create a new project that will filter out the old versioning. In the future I would like to introduce version streams, which could be used for major versions as well as for changes in versioning scheme. This should work as option for grouping versions together based on specified filter, which would be created by user, and setting specific version scheme for each version stream. |
Version streams would be the ideal solution to address this problem. Before that feature is implemented, if we delete the current project and recreate it, should I just put The filter doesn't seem to allow me to specify a regex to only match |
The filter is just looking for the pattern in string, so add anything that will filter the versions you don't need. You can use the |
It doesn't remove any version that is already in Anitya, just filtering new versions found upstream. |
Alright, I'll flag this project for deletion and recreate it afterwards, thanks. |
This is also a problem here: https://release-monitoring.org/project/155688/ 50.2 is the latest. |
Sometimes a project can switch to a different versioning scheme, and there does not seem to be a way to tell anitya which scheme is newer. Take UEFITool as an example, older versions with an old engine are versioned like
0.21.5
, while the versions with the new engine are versioned likeA63
. There is currently no way to make theA**
versions take precedence, and it would be nice to have a bit more control over how the releases are sorted.The text was updated successfully, but these errors were encountered: