Releases: maxmind/geoipupdate
Releases · maxmind/geoipupdate
Release list
7.1.1
7.1.0
- Allow the
Hostconfiguration directive and theGEOIPUPDATE_HOST
environment variable to accept a value with the scheme set. If not set, it
will continue to default tohttps://. Pull request by Gabe Cook. GitHub
#310. - Export
HTTPErrorto enable fine-grained error handling for users of
github.com/maxmind/geoipupdate/client. Pull request by Ryan Davis. GitHub
#341.
7.0.1
- 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
- BREAKING CHANGE: Improvements to the HTTP download API.
The client now calls two new endpoints:/geoip/updates/metadatawhich is responsible for getting information about
a database edition./geoip/databases/{edition-id}/downloadwhich is responsible for downloading
the content of a database edition. This new endpoint redirects downloads to R2
presigned URLs, so systems runninggeoipupdateneed to be able to
reach
mm-prod-geoip-databases.a2649acb697e2c09b632799562c076f2.r2.cloudflarestorage.com
in addition toupdates.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 aClientatgithub.com/maxmind/geoipupdate/clientwith a
Download()method. The intention is to expose less of thegeoipupdate
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_VERBOSEmust either be0or1.
All other values will return an error. - Setting
GEOIPUPDATE_VERBOSEto1now works as expected. In the 6.0.0 and
6.1.0 releases, the flag was ignored. Reported by pmcevoy. GitHub #298. geoipupdatenow supports retrying on more types of errors
such as HTTP2 INTERNAL_ERROR.- Now
geoipupdatedoesn'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
geoipupdatenow sets the version in theUser-Agentheader 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_FILEare ignored, see #262 issue.
6.0.0
-
geoipupdatenow 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_IDGEOIPUPDATE_ACCOUNT_ID_FILEGEOIPUPDATE_CONF_FILEGEOIPUPDATE_DB_DIRGEOIPUPDATE_EDITION_IDSGEOIPUPDATE_HOSTGEOIPUPDATE_LICENSE_KEYGEOIPUPDATE_LICENSE_KEY_FILEGEOIPUPDATE_LOCK_FILEGEOIPUPDATE_PARALLELISMGEOIPUPDATE_PRESERVE_FILE_TIMESGEOIPUPDATE_PROXYGEOIPUPDATE_PROXY_USER_PASSWORDGEOIPUPDATE_RETRY_FORGEOIPUPDATE_VERBOSE
-
Changed the signature of
NewConfiginpkg/geoipupdateto no longer accept
a positional config file path argument, which can now be passed in using the
option fromWithConfigFilealong with the other optional parameters. -
geoipupdateandNewConfigno longer require a config file to exist. -
The
--stack-traceflag has been removed. This flag has been broken since
4.11.0.
5.1.1
- 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
- Fixed the Docker health-check script to use the correct time of
the last update attempt. Reported by cford1080. GitHub #225. - Added new
--outputflag 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,
geoipupdateno longer runs
as root in the container. Based on pull request by Andreas
Grünenfelder. GitHub #200.
5.0.4
- 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
- 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/GeoIPwas being used rather than/usr/share/GeoIP.
This build restores/usr/share/GeoIPas the default directory for
these builds. Reported by Yvan. GitHub #222.