Per documentation, it’s possible to set a specific version for a build step using
--package step:version; however, is it possible to set it to a version range?
For example if we wanted the latest NuGet package available from the attached feed
--package step:* or anything above 1.0
Thanks for getting in touch! Unfortunately this isn’t possible, but after 3.0 we plan to add first class support for branching: http://octopusdeploy.com/blog/rfc-branching.
This will allow you to do something like
octo.exe create-release --branch master, and it will use your
master branching rules which can specify version ranges.
For now, you’ll have to be explicit about package version numbers.