0.11.0

Changed

• Include delimiters before slashes in URLs. E.g. in https://test.com/!/,
  we would previously only extract https://test.com/, whereas now we
  extract the full URL https://test.com/!/ (#90)

0.10.0

Added

• New option url_can_bi_iri that can be used to disable international
  domain parsing (still enabled by default). This is useful for parsing
  ASCII only URLs out of non-ASCII text even if there's no spaces
  before/after the URL (#49)

Changed

• Don't require valid hostname for file:// URLs to allow for relative
  paths used in the wild (#58)
• Support URIs with empty path but with query, e.g. foo://bar?a=b (#59)
• Require IPv4 addresses to have 4 numeric parts. This means things
  like 1.0 are no longer recognized as domains (#46)

0.9.0

Changed

• More strict parsing of hostname (authority) part of URLs. Applies to
  emails, plain domains URLs (e.g. example.com/foo) and URLs with
  schemes where a host is expected (e.g. https).

  This fixes a few problems that have been reported over time, namely:

  • https://www.example..com is no longer parsed as an URL (#41)
  • foo@v1.1.1 is no longer parsed as an email address (#29)
  • https://*.example.org is no longer parsed as an URL (#38)

  It's a tricky change and hopefully this solves some problems while
  not introducing too many new ones. If anything unexpectedly changed
  for you, please let us know!

0.8.1

Changed

• Skip parsing very short strings for URLs as a performance optimization