Release candidate versions

I’m having a problem in Octopus where the version number used by Octopus isn’t correct when previous release candidate versions exist. For example, I have already created a release with version and now want to create the official release using version Octopus will pick up the correct nuget package, but it fills the version number textbox with instead of

Of course, I can just change the version number value, but I’m sure that I’ll forget at least once. This behavior seems to have started after we upgraded to Octopus 2.0.

Hi Nick,

Yes, this was a change in 2.0 that’s improved some scenarios and detracted from others. I’ve added a ticket here with some explanations and possible remedies, any input appreciated: