1.0.11

Fix: pproxy changed their API without telling anyone (#27)

This library doesn't have a changelog, and clearly it saw a need
to change the API without letting anyone know.

1.0.10

Update: dependencies update (#26)

* Update aiohttp from 3.7.3 to 3.7.4
* Update botocore from 1.19.63 to 1.20.17
* Update idna from 2.10 to 3.1
* Update pproxy from 2.5.6 to 2.7.6
* Update pynamodb from 5.0.0 to 5.0.3
* Update sentry-sdk from 0.19.5 to 0.20.3

1.0.9

Fix: [Docker] update pip to latest when building image

1.0.8

Update: dependencies update (#22)

* Update aiohttp from 3.7.2 to 3.7.3
* Update attrs from 20.2.0 to 20.3.0
* Update botocore from 1.19.9 to 1.19.26
* Update certifi from 2020.6.20 to 2020.11.8
* Update multidict from 5.0.0 to 5.0.2
* Update pproxy from 2.3.7 to 2.4.6
* Update sentry-sdk from 0.19.1 to 0.19.4
* Update urllib3 from 1.25.11 to 1.26.2
* Update yarl from 1.6.2 to 1.6.3

1.0.7

Update: dependencies update (#21)

* Update aiohttp from 3.6.2 to 3.7.2
* Update botocore from 1.18.11 to 1.19.9
* Update multidict from 4.7.6 to 5.0.0
* Update openttd-helpers from 1.0.0 to 1.0.1
* Update sentry-sdk from 0.18.0 to 0.19.1
* Update urllib3 from 1.25.10 to 1.25.11
* Update yarl from 1.6.0 to 1.6.2

1.0.6

Update: dependencies update (#19)

1.0.5

Fix: update README to indicate you should set random AWS keys in deve…

1.0.4

Fix: close the UDP socket when we are done with it (#10)

The assumption was it would close when it got out of scope; but
this doesn't seem to be the case, resulting in systems running
out of file descriptors on production.

1.0.3

Fix: don't log every time a server is not responding (#9)

This happens often enough in production that it blurs the logs
from what is really going wrong. It turns out a lot of people
have their advertisement on, but they never really advertise.
This is most likely due to their firewall not allowing all
required traffic for a gameserver to be advertised.

1.0.2

Add: support SOCKS proxy for new outgoing connections (#7)

In the way we currently deploy this in production, it runs on
AWS ECS which does not support IPv6 for containers. As we query
game servers from the container, a new outgoing connection has
to be created which supports both IPv4 and IPv6. By using a SOCKS
proxy deployed within the AWS VPC, we can now query game servers
from within the container without AWS ECS supporting IPv6.

Of course as soon as AWS supports IPv6 for AWS ECS this can be
dropped.