Repository navigation
2.0.0 #2
Closed
rennf93
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Django API Guard 2.0.0 — guard-core Migration
Django API Guard is now a thin adapter over guard-core, the framework-agnostic security engine that also powers fastapi-guard and flaskapi-guard.
What changed
guard-core1.0.0). This package provides only the Django integration layer via standard Django middleware (__init__/__call__).cachetools,maxminddb,pydantic,redis, andrequestsare no longer direct dependencies (they come transitively throughguard-core).guard_core.sync.*modules for Django's synchronous request model.Zero breaking changes to the public API
All existing imports continue to work exactly as before:
Why v2.0.0
The major version bump reflects the architectural shift — guard-core is now a required dependency, and internal modules (djangoapi_guard.core., djangoapi_guard.handlers., djangoapi_guard.detection_engine.*)
no longer exist. If you only used the public API, no migration is needed.
One engine, three frameworks
All three share the same security engine, ensuring consistent behavior across frameworks.
Full Changelog: 1.0.1...2.0.0
This discussion was created from the release 2.0.0.
All reactions