Skip to content

Releases: faradayio/geocode-csv

v1.0.0 - 2021-12-13

13 Dec 12:40
@emk emk
Compare
Choose a tag to compare

Bumping number to v1.0.0 because this has been running fine in production for quite.

Added

  • Support --match enhanced. This only works for appropriate SmartyStreets plans.

Fixed

  • Updated dependencies to fix several CVEs reported by cargo deny. I do not believe that any of these CVEs actually affected geocode-csv in practice, but better safe than sorry.

v0.3.0-beta.5

21 May 12:13
Compare
Choose a tag to compare
v0.3.0-beta.5: Update to latest tokio

v0.3.0-beta.4

20 May 18:15
Compare
Choose a tag to compare
have travis use env var

v0.3.0-beta.1: Port to tokio 0.2, merge suffixes

27 Mar 15:05
@emk emk
Compare
Choose a tag to compare
This release is based on `tokio` 0.2, bringing all the async components
into the modern world.

We also add some code to fix a common pattern where addresses contain
"Main Street #302 #302" because of inconsistently  redundant columns.

v0.2.1

05 Dec 16:58
@emk emk
83175c1
Compare
Choose a tag to compare
Allow 'glob' as an alias for 'address'

v0.2.0: Add `--duplicate-columns`

19 Nov 15:03
@emk emk
Compare
Choose a tag to compare
The `--replace` flag from v0.2.0-alpha.1 has been removed. Instead, you
may now specify one of the following:

`--duplicate-columns=error` (default):
    Fail if any output columns already exist in the input CSV.
`--duplicate-columns=replace` (default):
    Remove any input columns which have the same name as output columns
    before geocoding.
`--duplicate-columns=append` (default):
    Just add the output columns and don't worry about duplicates.

Users migrating from 0.1.x should specify `--duplicate-columns=append`
if they want to maintain backwards compatibility.

This version also ships with a more extensive set of integration tests,
which actually run `geocode-csv` as a CLI tool, and which use the real
SmartyStreets API.

v0.2.0-alpha.1: Optionally remove existing geocode columns

18 Nov 11:51
@emk emk
Compare
Choose a tag to compare
If the geocoder would introduce columns that already exist in the file,
we do one of two things:

1. By default, we exit with an error.
2. If the user passes `--replace`, we strip any column with the same
   name as a geocoding output column, and add the output columns
   normally.

v0.1.2: Fix --help and --version

17 Jun 15:22
@emk emk
Compare
Choose a tag to compare
In v0.1.1, the `--version` was wrong and `--help` was missing 95% of the
necessary information.

v0.1.1: Fix release binary packaging

16 Jun 18:04
@emk emk
Compare
Choose a tag to compare
This release should fix a bug that prevented static binaries from being
released.