Releases: gadventures/django-gapi-hooked
0.6.0
What's Changed
- Test on all the Django 4.x versions (and Python 3.11) by @jonprindiville in #27
Full Changelog: 0.5.2...0.6.0
Stop validating 'href' for incoming events
0.5.0 (2017-09-11) via #18
-
The
href
of incoming webhook events is no longer validated. Rejecting an
event with an unexpectedhref
value would simply have resulted in
repeated attempts to deliver that event again. -
Incoming webhooks with incorrect signatures will be rejected by default and
an error will be logged. If you wish to accept webhooks with incorrect
signatures (and simply log a warning), setHOOKED_FAIL_ON_BAD_SIGNATURE
toFalse
If you believe that your webhook receiver is incorrectly rejecting webhooks,
please ensure that your webhook subscription is using the same application
key as is defined in your webhook receiver'sGAPI_APPLICATION_KEY
setting. -
Settings changes:
GAPI_API_ROOT
is no longer used by django-gapi-hookedHOOKED_FAIL_ON_BAD_SIGNATURE
defaults toTrue
instead ofFalse
Version fix & enabling Travis CI
0.4.0
- Add Python 3.5+ support (maintaining Python 2.7 support)
- Add MIT License, begin preparing
setup.py
for a release on PyPI - Add resource-name-based dynamic dispatch to
WebhookReceiverView
(e.g you
can define ahandle_profiles
method on your subclass and it will handle
profiles
events without having to write your own routing code, see README
for examples) - Add a (presently very small) test suite and a
tox.ini
to test multiple
Python/Django versions - Settings changes:
-
GAPI_API_ROOT
is no longer required, it defaults to
"https://rest.gadventures.com"
-
GAPI_APPLICATION_KEY
is now required -
GAPI_WEBHOOKS_VALIDATION_KEY
is no longer used at all (we compute this
value from your application key)
-
0.3.0
- Raise exceptions in
clean_events
instead of returning them (the caller is
expecting a list of webhook events, not an exception) - Updated README to explain required settings