Open chrischtel opened 3 months ago
There is no way afaik, but we plan to change the setup so that Nimble only considers commits that change the version inside the .nimble file as releases. This way no git tagging is required at all which is nice for workflows where the primary mode of development is by merging pull requests.
Is there a way to configure Nimble so that it does not treat every tag with a number in it as a new release? I want Nimble to only install a new version of my app when there is a v..* tag. My GitHub workflow uses tags like v0.1.6-rc for release candidates, but Nimble currently sees these as new releases.