Skip to content

Releases: maxmind/geoipupdate

7.1.0

18 Nov 17:55
662daf8
Compare
Choose a tag to compare
  • Allow the Host configuration directive and the GEOIPUPDATE_HOST
    environment variable to accept a value with the scheme set. If not set, it
    will continue to default to https://. Pull request by Gabe Cook. GitHub
    #310.
  • Export HTTPError to enable fine-grained error handling for users of
    github.com/maxmind/geoipupdate/client. Pull request by Ryan Davis. GitHub
    #341.

7.0.1

08 Apr 21:31
0df16c4
Compare
Choose a tag to compare
  • The 7.0.0 release was broken and has been retracted. This release updates the
    module path to match tagged version. Reported by Adam Weinberger. GitHub #306.

7.0.0

08 Apr 20:20
b647899
Compare
Choose a tag to compare
  • BREAKING CHANGE: Improvements to the HTTP download API.
    The client now calls two new endpoints:
    • /geoip/updates/metadata which is responsible for getting information about
      a database edition.
    • /geoip/databases/{edition-id}/download which is responsible for downloading
      the content of a database edition. This new endpoint redirects downloads to R2
      presigned URLs, so systems running geoipupdate need to be able to
      reach
      mm-prod-geoip-databases.a2649acb697e2c09b632799562c076f2.r2.cloudflarestorage.com
      in addition to updates.maxmind.com.
  • BREAKING CHANGE: The public package API has been redesigned. The previous
    API was not easy to use and had become a maintenance burden. We now
    expose a Client at github.com/maxmind/geoipupdate/client with a
    Download() method. The intention is to expose less of the geoipupdate
    internals and provide a simpler and easier to use package. Many
    previously exposed methods and types are now either internal only or have
    been removed.
  • BREAKING CHANGE: If set, GEOIPUPDATE_VERBOSE must either be 0 or 1.
    All other values will return an error.
  • Setting GEOIPUPDATE_VERBOSE to 1 now works as expected. In the 6.0.0 and
    6.1.0 releases, the flag was ignored. Reported by pmcevoy. GitHub #298.
  • geoipupdate now supports retrying on more types of errors
    such as HTTP2 INTERNAL_ERROR.
  • Now geoipupdate doesn't requires the user to specify the config file
    even if all the other arguments are set via the environment variables.
    Reported by jsf84ksnf. GitHub #284.

6.1.0

09 Jan 23:55
411fed0
Compare
Choose a tag to compare
  • geoipupdate now sets the version in the User-Agent header to the
    version in the binary. While there were no issues with the version in the
    header, this makes sure it will match the binary. The header also now
    includes build information, such as OS and architecture.
  • White spaces in secret files GEOIPUPDATE_ACCOUNT_ID_FILE,
    GEOIPUPDATE_LICENSE_KEY_FILE are ignored, see #262 issue.

6.0.0

12 Jul 19:14
62d961e
Compare
Choose a tag to compare
  • geoipupdate now supports configuration via environment variables. Any
    configuration set this way will override any value from the config file,
    but still be overridden by any associated command line option (if any).
    The following new environment variables are supported:

    • GEOIPUPDATE_ACCOUNT_ID
    • GEOIPUPDATE_ACCOUNT_ID_FILE
    • GEOIPUPDATE_CONF_FILE
    • GEOIPUPDATE_DB_DIR
    • GEOIPUPDATE_EDITION_IDS
    • GEOIPUPDATE_HOST
    • GEOIPUPDATE_LICENSE_KEY
    • GEOIPUPDATE_LICENSE_KEY_FILE
    • GEOIPUPDATE_LOCK_FILE
    • GEOIPUPDATE_PARALLELISM
    • GEOIPUPDATE_PRESERVE_FILE_TIMES
    • GEOIPUPDATE_PROXY
    • GEOIPUPDATE_PROXY_USER_PASSWORD
    • GEOIPUPDATE_RETRY_FOR
    • GEOIPUPDATE_VERBOSE
  • Changed the signature of NewConfig in pkg/geoipupdate to no longer accept
    a positional config file path argument, which can now be passed in using the
    option from WithConfigFile along with the other optional parameters.

  • geoipupdate and NewConfig no longer require a config file to exist.

  • The --stack-trace flag has been removed. This flag has been broken since
    4.11.0.

5.1.1

08 May 16:19
4af64e2
Compare
Choose a tag to compare
  • Based on feedback, the change to use a non-root user in 5.1.0
    when using the Docker image has been reverted. There are no
    non-Docker changes in this release. See GitHub #233.

5.1.0

05 May 22:21
30b4c30
Compare
Choose a tag to compare
  • Fixed the Docker health-check script to use the correct time of
    the last update attempt. Reported by cford1080. GitHub #225.
  • Added new --output flag to print JSON to standard output describing
    the result of the run.
  • Compilation with Go versions before 1.19 is no longer supported.
  • When using the provided Docker images, geoipupdate no longer runs
    as root in the container. Based on pull request by Andreas
    Grünenfelder. GitHub #200.

5.0.4

17 Apr 16:20
8b3f7d6
Compare
Choose a tag to compare
  • On releases 4.9.0 through 5.0.3, the incorrect commit was tagged.
    This release attempts to fix the release process to prevent this
    issue. There are no code changes to the binaries provided by
    MaxMind, either on the GitHub Release page or the MaxMind PPA.

5.0.3

15 Apr 13:47
207be04
Compare
Choose a tag to compare
  • On 5.0.0 through 5.0.2, the default database directory was not being
    correctly set for Debian and RPM package builds. The directory
    /usr/local/share/GeoIP was being used rather than /usr/share/GeoIP.
    This build restores /usr/share/GeoIP as the default directory for
    these builds. Reported by Yvan. GitHub #222.

5.0.2

13 Apr 16:54
2227ee2
Compare
Choose a tag to compare
  • "Database ... up to date" messages are now only shown if the verbose
    flag is set. Pull request by Adam Weinberger. GitHub #219.