<commit_before># Changelog

Each release is divided into the following main categories:

- IMPORTANT: These changes might not be backward compatible and require updating existing code. (If not applied correctly your update will fail)
    - SETTINGS: change your setting.py accordingly
    - TEMPLATES: if templates form allink_core are overridden, you have to double apply these changes
    - URLS: changes to urls.py
    - REQUIREMENTS: new or changed requirements
    - DATA MIGRATIONS: stuff to migrate by hand or create data migrations manually
- NEW: New features or plugins
- FIXES: General bugfixes

The version numbers referring to the version in [allink_core](<EMAIL>/allink/allink-core.git).


## v0.0.9 (under development)

### IMPORTANT

###### SETTINGS

###### TEMPLATES

###### URLS

###### REQUIREMENTS

###### DATA MIGRATIONS

- when making migrations on projects it's important, that the field "active" on each model gets renamed to "is_active".
  The field must not be deleted and created as new, else data gets lost

### NEW

### FIXES

- field "active" renamed to "is_active" on all models

## v0.0.8

### IMPORTANT

###### SETTINGS

###### TEMPLATES

###### URLS

###### REQUIREMENTS

###### DATA MIGRATIONS<commit_msg>category nav in case no categories are selected fixed<commit_after># Changelog

Each release is divided into the following main categories:

- IMPORTANT: These changes might not be backward compatible and require updating existing code. (If not applied correctly your update will fail)
    - SETTINGS: change your setting.py accordingly
    - TEMPLATES: if templates form allink_core are overridden, you have to double apply these changes
    - URLS: changes to urls.py
    - REQUIREMENTS: new or changed requirements
    - DATA MIGRATIONS: stuff to migrate by hand or create data migrations manually
- NEW: New features or plugins
- FIXES: General bugfixes

The version numbers referring to the version in [allink_core](<EMAIL>/allink/allink-core.git).


## v0.0.9 (under development)

### IMPORTANT

###### SETTINGS

###### TEMPLATES

###### URLS

###### REQUIREMENTS

###### DATA MIGRATIONS

- when making migrations on projects it's important, that the field "active" on each model gets renamed to "is_active".
  The field must not be deleted and created as new, else data gets lost

### NEW

### FIXES
- field "active" renamed to "is_active" on all models
- category nav in case no categories are selected fixed

## v0.0.8

### IMPORTANT

###### SETTINGS

###### TEMPLATES

###### URLS

###### REQUIREMENTS

###### DATA MIGRATIONS
{'fraction_non_alphanumeric': 0.10446601941747573, 'fraction_numerical': 0.004660194174757282, 'mean_word_length': 4.141716566866267, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7094893', 'n_tokens_mistral': 781, 'n_tokens_neox': 726, 'n_words': 314}