chore(release): 0.2.0

CHANGELOG.md

@@ -6,9 +6,14 @@ All notable changes to Diskern are documented here. The format follows
 
 ## [Unreleased]
 
+## [0.2.0] — 2026-09-07
+
 ### Added
 
-- `diskern scan --rules <file>` to test scans with an external rules database
+- `diskern scan --rules <file>` to test scans with an external rules
+  database. Patterns are validated before the scan starts, and the
+  embedded `protected` rules stay in front of the supplied ones, so a
+  rules file can add coverage but never shadow a system-critical path
 - Cancel a running scan from the desktop app
 - `diskern scan` prints the findings themselves — grouped by verdict and
   category, with `--top` to cap each group and `--verdict` to filter
@@ -59,6 +64,11 @@ All notable changes to Diskern are documented here. The format follows
   cancelled scan can't leave it emitting for the rest of the process
 - Two files that flatten to the same quarantine name no longer overwrite
   each other
+- Purging an empty quarantine is a no-op rather than an error
+- A directory holding two project markers (`Cargo.toml` and
+  `package.json`, say) is recognised as both kinds rather than whichever
+  the walk happened to see last, which had made the verdict on its build
+  output depend on walk order
 
 ## [0.1.0]
 

Cargo.toml

@@ -7,7 +7,7 @@ members = [
 ]
 
 [workspace.package]
-version = "0.1.0"
+version = "0.2.0"
 edition = "2021"
 license = "MIT"
 repository = "https://github.com/Coding-Moves/diskern"

app/package.json

@@ -1,7 +1,7 @@
 {
   "name": "diskern-app",
   "private": true,
-  "version": "0.1.0",
+  "version": "0.2.0",
   "type": "module",
   "scripts": {
     "dev": "vite",

app/src-tauri/tauri.conf.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://schema.tauri.app/config/2",
   "productName": "Diskern",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "identifier": "com.diskern.app",
   "build": {
     "beforeDevCommand": "npm run dev",