Release 0.2.1

CHANGELOG.md

@@ -11,23 +11,22 @@ documentation, and CI work are left out.
 
 ## [Unreleased]
 
+## [0.2.1] — 2026-08-19
+
 ### Added
 
-- The running app version is shown at the bottom of every screen, so a bug
-  report no longer needs `GET /api/v1/status`.
+- The running app version is shown at the bottom of every screen.
 
 ### Changed
 
-- **Bereiche schwärzen** now draws on the redacted pages, so the automatic text
-  redactions are visible while marking areas; scanned documents draw on the
-  reconstruction, which is the page their areas are applied to — see
+- **Bereiche schwärzen** draws on the redacted pages, so the automatic
+  redactions are visible while marking areas — see
   [Reviewing a result](docs/user-guide/review.md).
 
 ### Fixed
 
-- An area drawn on a scanned document's export removed only the pixels: the
-  reconstructed text under the black box stayed selectable. Areas are now true
-  redactions on both PDF paths, verified before the export is handed out.
+- Areas drawn on a scanned document's export only covered the text instead of
+  removing it, leaving it selectable in the exported PDF.
 
 ## [0.2.0] — 2026-08-11
 
@@ -146,6 +145,7 @@ First tagged version.
   configurable deployment banner sits above the header.
 - Documentation site (MkDocs Material) under `docs/`.
 
+[0.2.1]: https://github.com/KatherLab/deidentifier/compare/v0.2.0...v0.2.1
 [0.2.0]: https://github.com/KatherLab/deidentifier/compare/v0.1.3...v0.2.0
 [0.1.3]: https://github.com/KatherLab/deidentifier/compare/v0.1.2...v0.1.3
 [0.1.2]: https://github.com/KatherLab/deidentifier/compare/v0.1.1...v0.1.2

CITATION.cff

@@ -45,8 +45,8 @@ keywords:
   - "privacy-preserving artificial intelligence"
 
 license: "AGPL-3.0-or-later"
-version: "0.2.0"
-date-released: "2026-08-11"
+version: "0.2.1"
+date-released: "2026-08-19"
 
 references:
   - type: article

THIRD_PARTY_NOTICES.md

@@ -1,6 +1,6 @@
 # Third-Party Notices
 
-The Medical Document Anonymizer (version `0.2.0`) is distributed
+The Medical Document Anonymizer (version `0.2.1`) is distributed
 under the `AGPL-3.0-or-later` license. It bundles the third-party
 open-source components listed below, each governed by its own license.
 Full license texts are available in each project's repository (linked

backend/src/core/config.py

@@ -41,7 +41,7 @@ class Settings(BaseSettings):
 
     # Application
     APP_ENV: str = "development"
-    APP_VERSION: str = "0.2.0"
+    APP_VERSION: str = "0.2.1"
     APP_MAX_UPLOAD_MB: int = Field(default=20, ge=1)
     APP_MAX_TEXT_CHARS: int = Field(default=500_000, ge=1)
     APP_ALLOW_INSECURE_CONTENT_LOGGING: bool = False

docs/operations/deployment.md

@@ -20,8 +20,8 @@ has been published to `ghcr.io`, a deployment host can skip the build
 toolchain entirely:
 
 ```bash
-DEIDENTIFIER_IMAGE_TAG=v0.2.0 docker compose pull
-DEIDENTIFIER_IMAGE_TAG=v0.2.0 docker compose up -d
+DEIDENTIFIER_IMAGE_TAG=v0.2.1 docker compose pull
+DEIDENTIFIER_IMAGE_TAG=v0.2.1 docker compose up -d
 ```
 
 You still need `compose.yml` and your `.env` on that host.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "deidentifier",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "private": true,
   "description": "Deidentifier frontend — anonymize German clinical documents locally.",
   "license": "AGPL-3.0-or-later",

pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "deidentifier"
-version = "0.2.0"
+version = "0.2.1"
 description = "Locally deployable anonymizer for German clinical documents"
 requires-python = ">=3.13,<3.15"
 # Every dependency is pinned exactly, like the frontend's package.json: this is