Releases: k0rventen/flask-gatekeeper
v1.0.0: Major breaking changes !
This release breaks compatibility with pre-1.0.0.
- args to Gatekeeper() are different both in names and types.
- the custom return funcs have been deleted
- specific HTTP methods can be ignored through
excluded_methods
Other notable changes:
- the test suite is simplified and covers more use cases
- the inline doc is improved and more of it is shown on the rendered docs
- test matrix for python 3.7 to 3.10
v0.3.3, custom return funcs & better docs
- add support for custom return functions in the Gatekeeper constructor
- auto-generated sphinx documentation to GitHub Pages
- tests for python 3.10
Full Changelog: v0.3.2...v0.3.3
v0.3.2, housekeeping and fix
mainly housekeeping and fixing a mistake where reporting an ip would increase it's requests count by one.
v0.3.1! supports flask 2!
This small release adds support for flask 2, and requires at least python 3.7.
v0.3.0! increased timing precision
this moves all timestamps to float instead of ints, avoiding some same-second weir behaviour.
This also fixes a mixup in arguments, where the ban duration & ban window were inverted. A GateKeeper instance now reads properly the ban_rule list.
small fix
v0.2 ! Supports bypass & route specific gatekeepers
You can now decorate a route with bypass
to ignore this route from rate-limiting.
When using the specific()
decorator, you can set standalone=True
, so that the global rate limit rule does not apply to it.
Unit tests have also been added.
first published version
0.1 pypi ci push