Trying to work with prerelease

[rubenvereecken]

I have

1.0.55+132

I want

1.0.55+132-alpha
or
1.0.55+132-alpha.1 

I expected to be able to use

cider bump pre --pre=alpha

except that doesn't seem supported.
Also note how I'm increment build because this is an internal build, where the build number doesn't need incrementing.

---

For our beta channel I wanted to do something similar, except that's on public channels (Google Play, TestFlight), so it does need the build number incremented.

> cider bump build --pre=beta

Unhandled exception:
The next version must be higher than current

I suppose you're right if you want to enforce that.. Though for us it makes a lot of sense to only bump the prerelease version while also bumping the build number, even though that might not match some invariant that seems to be enforced here. Probably inspired by semver.

While I'm at it, this might be a bug

> cider bump patch -b --pre=alpha 

Null check operator used on a null value
#0      CommandRunner.parse (package:args/command_runner.dart:134:51)
#1      CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:119:36)
#2      new Future.sync (dart:async/future.dart:218:31)
#3      CommandRunner.run (package:args/command_runner.dart:119:14)
#4      Cider.run (package:cider/src/cider.dart:67:33)
#5      main (file:///home/ruben/.pub-cache/hosted/pub.dartlang.org/cider-0.1.0/bin/cider.dart:6:13)
#6      _delayEntrypointInvocation.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:281:32)
#7      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:184:12)

Can we talk about how to achieve some of these very practical use cases?