Thanks for getting in touch! Sorry to say there’s no way to specify a version range in the
octo create-release command, and I imagine the closest to what you’re after is to specify the individual package version via
Generally with requirements like this, we do often suggest the use of the channels feature in order to control which package versions are used between them. These rules can have a large version range defined (along with controlling based on pre-release tag), so they should be longer lived than a channel for just a single version.
I’d be interested to hear more about your requirements and goals, and we’ll be happy to help model the best approach.
I hope this helps for now, and I look forward to hearing back!