RFC: Add option to hex.retire to retire or unretire a group of releases

[supersimple]

I have a use-case where I want to retire all 1.x versions of a package. Rather than individually retiring each release, I was hoping to do them all at the same time. I think the common action is just to retire the most recent release which would not show the flag in the CLI nor the banner on hexpm if a user is a point release behind.

My initial idea was mix hex.retire PKG VER --major or mix hex.retire PKG VER --minor which would apply the retirement to all releases in that major version or minor version.

Another idea is to have --to and --from options which would accept a range of versions.

Thoughts?

[wojtekmach]

To me this doesn't seem to be a common enough use case to justify adding more code. I'd suggest to solve it with a little scripting:

for v in 1.0.0 1.0.1 1.0.2; do mix hex.retire $pkg $v $reason --message "$message"; done

fwiw when using mix hex.info we'd only get several recent versions and there isn't another built-in way to get all published versions. We can get them from API easily though:

~% curl --silent https://hex.pm/api/packages/ecto | jq ".releases[].url" | tr -d '"' | cut -d/ -f8 | grep ^1
1.1.9
1.1.8
1.1.7
(...)

[supersimple]

@ericmj I will close this later today unless you want to discuss it further. I see some value in the feature, but I respect the maintainers opinion on not want to add complexity to the project for little gain.

[ericmj]

Thanks for the feature request, let's wait and see if we get similar requests and maybe we can nail down a good API when we have more use cases.