ipinfo-2.2.0

• ipinfo now supports file-based caching by default. All requests will be
  cached for 24 hours, and the maximum cache file size will be 1GB before
  pruning automatically occurs.
  • You may disable the cache with --nocache on any command that would
    otherwise use it.
  • You can manually clear the cache with ipinfo cache clear.
  • We will add more capabilities and configuration to the cache in future
    releases.
• ipinfo <domain> is now allowed, e.g. ipinfo google.com, which will lookup
  the IP address found at google.com.
• ipinfo's field selection flag -f/--field can now accept multiple fields
  separated by commas, including repeatedly, e.g.
  ipinfo 1.1.1.1 -f ip,asn,privacy,company.type.
• ipinfo prips now allows piping in input the same exact way as ipinfo bulk
  and other commands that take IP inputs.
• When inputting files via stdin or arguments for commands like ipinfo bulk,
  ipinfo map, etc., the files may now also contain CIDRs & IP ranges which
  will be converted into individual IPs.
• ipinfo login now also accepts the token as the first argument, e.g.
  ipinfo login <token>.
• ipinfo login now checks if the token you're logging in with is actually
  valid, by checking via an IPinfo API endpoint.
• When login is required for some features, error messages shown when logged
  out now indicate that login is required.
• Fix a bug in ipinfo summarize where percentage calculations were off when
  the total IP count did not match the unique IP count.
• Fix a bug in grepip where -o doesn't properly handle outputting lines
  where more than 2 IPs were on the same line being parsed.
• Fix a bug in grepip where it could crash due to a too-lenient IPv4 parser.
• When cidr2range accepts a file, it now also looks to see if there is a
  header in CSV form, and if so changes the first column to range, just as it
  changes the first non-header columns from CIDRs to IP ranges.
• When range2cidr accepts a file, it now also looks to see if there is a
  header in CSV form, and if so changes the first column to cidr, just as it
  changes the first non-header columns from IP ranges to CIDRs. NOTE: this
  will work even if the IP range takes up 2 columns as in start_ip,end_ip,
  in which case both columns are replaced by a single column cidr.
• Support for plan9 builds will be removed in future releases for the
  separate commands cidr2range, range2cidr and grepip, and will be
  dropped right now for ipinfo. Please see the following issue for details:
  etcd-io/bbolt#231