Releases: geopython/GeoHealthCheck
0.9.0
Many (58!) issues and PRs went in. Also thanks to contributors some major features
were added:
- configurable Geocoder (by @borrob)
- CI (from Travis CI) and Docker build/push migrated to Github Workflows
- OGC 3DTiles Probe (by SpotInfo)
- MapBox TileJSON Probe (by SpotInfo)
- additional WMTS Probes (by SpotInfo)
- use official OGC naming for OAFeat Probes (includes DB-upgrade)
- many bugfixes and security updates
Only a single DB-upgrade is required and only if your installation (DB) contains
OGC OAFeat Resources and Probes, formerly called "WFS3".
0.8.3
See all issues/PRs that went into this release in Milestone no 9.
This is a point release mainly for bug-fixing and small enhancements on 0.8.0 (we skipped 0.8.1 and 0.8.2).
Highlights
- #312 upgrade to OWSLib 0.2.0, mainly for allowing
headers
params and OAFeat client lib - finalize authentication both for webapp and Resources
- OAFeat Probes: use correct media types from metadata in content negotiation
- #336 Probes more web-friendly: add
User-Agent
andAccept-Encoding
HTTP headers for all Probes - German translation patches (thanks to @astroidex)
- quickfix Py3 encoding basic auth string
0.8.0
See all issues/PRs that went into this release in Milestone 0.8.0.
Highlights
- premier is the migration from Python 2 to (only) Python 3
requests
Session
HTTP-retries to limit "false negatives": PR #319 for issue #133
Upgrade notes
- no DB-upgrades from 0.7.0 are required
Note that the 0.7.0 release was the last release with Python 2 (only) support. 0.8.0+ will support only Python 3.
0.7.0
See all 40 issues/PRs that went into this release in Milestone 0.7.0.
Highlights
- mainly bugfixes
Upgrade notes
- no DB-upgrades from 0.6.0 are required
- #299: Include
HttpStatusNoError
as firstCheck
in mostProbes
. You may want to update your existing Probes to have this as firstCheck
, to also catch this error as this happens quite a lot
Note that the 0.7.0 release is the last release with Python 2 support.
0.6.0
This release is based on Milestone 6
A full list of issues that went into this release can be found at https://github.com/geopython/GeoHealthCheck/milestone/6?closed=1
This release requires a DB upgrade when upgrading from previous versions like 0.5.0. Running paver upgrade
is required when upgrading to 0.6.0. DB upgrade is performed automatically when upgrading your Docker image. The 0.5.0 to 0.6.0 DB upgrade is required to store passwords encrypted, encrypting existing passwords. See also the upgrade notes for 0.6.0.
26 issues and PRs went into this release, highlights:
- password encryption
- password recovery via password reset
- 2 new
Probes
for new OGC WFS3 (OGC Features API)Resource
type - improved/interactive Resource Run history visualization (using plotly.js)
- page loading performance improvements
- Croatian translations (thanks to @dracic)
- bug fixes CSV and JSON reporting
0.5.0
This release is based on Milestone 5 and provides a major upgrade, also architectural: see issue #132 and its resolution via PR #222 .
These are related to running Probes (healthchecks) in their own schedule (i.s.o. via cron
).
See the documentation for the new architecture.
A full list of issues that went into this release can be found at https://github.com/geopython/GeoHealthCheck/milestone/5?closed=1
This release requires a DB upgrade when upgrading earlier versions. Running paver upgrade
is required when upgrading to 0.5.0. DB upgrade is performed automatically when upgrading your Docker image.
Also note the new/changed options for running GHC in the relevant documentation.
0.4.0
This release provide numerous enhancements and bug fixes. A full
list can be found at https://github.com/geopython/GeoHealthCheck/milestone/4?closed=1
This release requires a DB upgrade when upgrading from 0.3.0 (in reference to #187 and #15). Running paver upgrade
is required when upgrading to 0.4.0.
0.3.0
This release provide numerous enhancements and bug fixes. A full
list can be found at https://github.com/geopython/GeoHealthCheck/milestone/3?closed=1
This release requires a DB upgrade when upgrading from 0.2.0 (#161). Running paver upgrade
is required when upgrading to 0.3.0.
Version 0.1.0 - first alpha version
The very first version of GeoHealthCheck: including first version of Plugins and Tags, that were not available on GitHub versions before May 1, 2017. More regular versions will follow. See documentation for instructions.