You can now drop prereleases and releases in one command

[teneko]

• Function AnyReleaseBefore in class Drop added
• Using named parameter now to clarify proper usage of function DropBefore

[taori]

Still trying to figure out why the pipeline is suddenly failing. apparently something changed when .net5 came around

[taori]

@teroneko Ok. Fixed the CI issue. However the checks fail since you did the changes on your forks master branch. In case you've previously not done this i would recommend you do the following:

• Create branch (e.g. "feature-anyreleasebefore") on your fork,
• pull state of my forks master branch
• insert changes from your current master
• Add PR which merges your branch into this master

Alternatively you can just copy the azure-pipelines.yaml since that is the only thing i changed. I would however recommend the usual workflow, since that is how you can merge to any repo with less conflicts.

The pipeline now checks properly so once you've done this i can merge it and push a release afterwards.

[teneko]

Mhh intereseting. Normally it shouldn't be a problem to accept the pull request regardless from whatever branch I want to pull request unless I do further changes and want to pull request that separately; that's definitely problematic. Whatsoever it is pretty solid to follow the git flow principles.