Heksher

Latest version: v0.2.2

Safety actively analyzes 681775 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 4

0.5.7

Internal
* upgrade to python 3.11
* support for newest sqlalchemy

0.5.3

Changed
* reverted the limited user introduced in 0.5.2 since it breaks older docker systems

0.5.2

Changed
* sending unknown context features in a query is no longer an error
* httpx is now a dev-dependency
* Docker container now runs with a limited user
Fixed
* returning 304 no longer logs an error "Too much data for declared Content-Length"
* most logs were incorrectly sent under the wrong logger name

0.5.1

Added
* Added a generic handler for unhandled errors
Fixed
* fixed an issue where the version would be blank in api
Internal
* image size has been reduced
* updated dependencies
* now based on python 3.10

0.5.0

Removed
* old api endpoint POST /api/v1/rules/query has been removed and replaced with GET /api/v1/query
Changed
* the rename api endpoint has been changed to PUT /api/v1/<name>/name.
* the method of the endpoint /api/v1/rules/search has been changed to GET.
* All setting now must have a default value.
* Setting declarations are now versioned.
* `HEKSHER_STARTUP_CONTEXT_FEATURES` is now optional.
* The inputs value for add_rule, value for patch_rule, value for put rule metadata key, value for
put setting metadata key, are now required.
Deprecated
* The api endpoint PATCH /api/v1/rules/<rule> to change a rule's value is now deprecated, new users
should use PUT /api/v1/rules/<rule>/value
Added
* declarations are now tolerant of subtypes (to account for previous type upgrade)
* documentation
* Added endpoint PUT /api/v1/settings/<name>/configurable_features
* The api endpoint PUT /api/v1/rules/<rule>/value to change a rule's value
* The api endpoint GET /api/v1/query to query rules (replaces the old query endpoint)
* POST /api/v1/rules now returns the rule location in the header
* added DOC_ONLY mode, read more about in the documentation
Fixed
* A bug where patching a context feature's index using "to_before" would use the incorrect target.
Internal
* a new script to test and correctly report coverage
* tools/mk_revision.py to easily create alembic revisions
* all db logic refactored to avoid multiple connections
* Many more column are now strictly non-nullable
* async-asgi-testclient is now a dev-dependency.
* added proper image tests

0.4.1

Removed
* removed the alembic extra, it's now a requirement

Page 1 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.