@mikem any better idea for naming? I'm not happy with this, but not sure how to improve it.

It is potentially misleading to have --non-latest as a boolean option and --latest as an int. Also, it's worth noting we have separate --latest-n and --latest for the list-tagged command. Granted a boolean --latest for this command is the default behavior, but I guess it would cancel out a --non-latest.

I don't love the "latest_n" name, but we do have prior art. Might be best to mimic the list-tagged args.

Updated.

You seem to have changed the default behavior to include all builds. This is not what we want.

Previously we had --non-latest which is unfortunately named. It was a boolean option that caused us to include all builds in the inheritance. This was not the default behavior and should not be. By default, we should only include the latest builds.

We don't really need a --latest option here, since this is the default behavior. I suggested it as a no-op for consistency with list-tagged, but in retrospect it's probably more confusion than its worth. The default latest behavior for list-tagged is different.

The simplest version of this fix is to leave --non-latest alone and simply add --latest-n to allow users to specify the requested behavior.

@mikem updated

this version seems fine. I'm not sure if the options really need to conflict, but I guess it isn't a problem if they do.

Looks like the unit tests need update

@mikem unit tests updated

Commit 134ec54d fixes this pull-request