You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
8
8
## [Unreleased]
9
9
10
+
**NOTE**: this release contains migrations. See [Upgrade to v1.4](https://florimondmanca.github.io/djangorestframework-api-key/upgrade/1.4/) for detailed instructions.
11
+
12
+
### Added
13
+
14
+
- The `prefix` and `hashed_key` are now stored in dedicated fields on the `APIKey` model.
15
+
10
16
## [v1.3.0] - 2019-06-28
11
17
12
18
**NOTE**: this release contains migrations. In your Django project, run them using:
The 1.4 release includes a migration that adds and populates the `prefix` and `hashed_key` fields to API keys.
6
+
7
+
This document lists the steps necessary to upgrade from 1.3.x to 1.4.
8
+
9
+
## Steps
10
+
11
+
### 1. Migrate the built-in API key model
12
+
13
+
The `APIKey` model can be migrated using the migration shipped with this package:
14
+
15
+
```bash
16
+
python manage.py migrate rest_framework_api_key
17
+
```
18
+
19
+
### 2. Migrate custom API key models (if applicable)
20
+
21
+
If you have a custom API key model deriving from `AbstractAPIKey`, you need to **manually add the migration** to your application.
22
+
23
+
- Copy the migration script below to your app's `migrations/` directory. Be sure to modify `APP_NAME`, `MODEL_NAME` and `DEPENDENCIES` as seems fit. You can name the migration script `xxxx_prefix_hashed_key.py` (replace `xxxx` with the next available migration ID).
0 commit comments