docs: rename 0.4.0 -> 0.5.0 across all docs after release-it minor bump

release-it auto-incremented 0.4.0 -> 0.5.0 because the
@release-it/conventional-changelog plugin saw `feat:` commits in the
range since v0.3.1 and inferred a minor bump. The published artefact
on npm is therefore `react-native-nitro-unzip@0.5.0` (latest), not
0.4.0. All CHANGELOG, README, docusaurus, and TypeScript-spec docstring
references that named 0.4.0 are renamed accordingly so the docs match
the npm/git-tag reality.

Anchor links (`#transactional-behaviour-040`, `#whats-new-in-040`)
updated to the new heading slugs.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: isaacrowntree

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## 0.4.0 — Cross-platform security hardening (Android NIO/ZipFile + iOS ZIPFoundation)
+## 0.5.0 — Cross-platform security hardening (Android NIO/ZipFile + iOS ZIPFoundation)
 
 **Breaking changes** — please read before upgrading.
 
@@ -54,7 +54,7 @@ with iOS/Swift primitives (not a Java translation):
 - **Password ZIP crypto upgraded to AES-256 on iOS.** 0.3 used
   SSZipArchive's `withPassword:` overload which writes traditional
   PKWARE encryption — broken, crackable in minutes with modern tools.
-  0.4.0 uses SSZipArchive's `aes: true` overload to match Android's
+  0.5.0 uses SSZipArchive's `aes: true` overload to match Android's
   AES-256 strength. Cross-platform password archives now have
   equivalent crypto.
 - **Mid-extraction cancellation on the password path now reads the
@@ -114,7 +114,7 @@ with iOS/Swift primitives (not a Java translation):
   `createDirectory(withIntermediateDirectories: true)` (iOS) and
   `Files.createDirectories` (Android) created every missing parent in
   one call, but rollback only knew about the leaf — orphaned empty
-  parents survived. 0.4.0 walks ancestry one level at a time and
+  parents survived. 0.5.0 walks ancestry one level at a time and
   records each created directory.
 - **Write errors propagate instead of being silently swallowed.** The
   iOS unzip path used `try? handle.write(contentsOf:)` inside the

README.md

@@ -13,7 +13,7 @@ High-performance ZIP operations for React Native, powered by [Nitro Modules](htt
 
 ## Features
 
-- **Fast** — ~9,000+ files/sec on Android (post-NIO / `java.util.zip.ZipFile` migration in 0.4.0) and ~10,000+ files/sec on iOS (`O_NOFOLLOW` streaming writes), measured on nested 1000-entry archives on dev hardware
+- **Fast** — ~9,000+ files/sec on Android (post-NIO / `java.util.zip.ZipFile` migration in 0.5.0) and ~10,000+ files/sec on iOS (`O_NOFOLLOW` streaming writes), measured on nested 1000-entry archives on dev hardware
 - **Zero bridge overhead** — progress callbacks via JSI, no serialization
 - **Cancellable** — mid-write cancellation on Android (`Thread.interrupt()` + interruptible NIO channels), per-entry cancellation on iOS (Swift Concurrency)
 - **AES-256 password support** — encrypted archives, zip & unzip, on both platforms
@@ -28,11 +28,11 @@ npm install react-native-nitro-unzip react-native-nitro-modules
 cd ios && pod install
 ```
 
-> Requires React Native 0.75+, [Nitro Modules](https://nitro.margelo.com/) 0.35+, iOS 15.5+, **Android minSdk 26+** (since 0.4.0), and Java 17 (Android).
+> Requires React Native 0.75+, [Nitro Modules](https://nitro.margelo.com/) 0.35+, iOS 15.5+, **Android minSdk 26+** (since 0.5.0), and Java 17 (Android).
 
-### Security defences (0.4.0+)
+### Security defences (0.5.0+)
 
-The 0.4.0 release added the same Zip Slip / symlink / case-collision /
+The 0.5.0 release added the same Zip Slip / symlink / case-collision /
 BiDi-spoofing defences to **both Android and iOS**:
 
 - Path traversal (`../escape`), absolute paths, backslash separators

docs/docs/getting-started.md

@@ -13,7 +13,7 @@ react-native-nitro-unzip provides high-performance ZIP extraction and compressio
 | React Native | 0.75+ |
 | Nitro Modules | 0.35+ |
 | iOS | 15.5+ |
-| Android SDK | **26+** (bumped in 0.4.0 — `java.nio.file` requires API 26) |
+| Android SDK | **26+** (bumped in 0.5.0 — `java.nio.file` requires API 26) |
 | Java (Android) | 17 |
 
 :::info New Architecture Required
@@ -39,7 +39,7 @@ The underlying `SSZipArchive` dependency requires **iOS 15.5+**. Set your deploy
 
 ### Android
 
-No additional setup needed — the library auto-links with React Native. Your app must be built with **Java 17** (the RN 0.73+ default) and target **`minSdkVersion 26`** or higher (bumped from 21 in 0.4.0 because the extraction path uses `java.nio.file.Path` / `Files` / `FileChannel`, which require API 26).
+No additional setup needed — the library auto-links with React Native. Your app must be built with **Java 17** (the RN 0.73+ default) and target **`minSdkVersion 26`** or higher (bumped from 21 in 0.5.0 because the extraction path uses `java.nio.file.Path` / `Files` / `FileChannel`, which require API 26).
 
 ## Quick Start
 

docs/docs/performance.md

@@ -8,7 +8,7 @@ react-native-nitro-unzip is designed for speed. Here's how it performs and why.
 
 ## Benchmarks
 
-### 0.4.0 nested perf smoke (1000 entries across ~512 unique dirs)
+### 0.5.0 nested perf smoke (1000 entries across ~512 unique dirs)
 
 Measured on dev hardware. Reflects realistic workloads (tile sets, asset bundles, SDK archives) — files spread across deep directory trees with many shared parent prefixes, not a flat archive.
 
@@ -17,7 +17,7 @@ Measured on dev hardware. Reflects realistic workloads (tile sets, asset bundles
 | Android (post-NIO) | ~8,300 files/sec | ~120 ms |
 | iOS (`O_NOFOLLOW` streaming write) | ~10,000+ files/sec | ~100 ms |
 
-The Android number is a **20× improvement** over the 0.3.x `ZipInputStream`-based path (~474 files/sec). The full 0.4.0 migration ([details](#whats-new-in-040)) is what made it possible.
+The Android number is a **20× improvement** over the 0.3.x `ZipInputStream`-based path (~474 files/sec). The full 0.5.0 migration ([details](#whats-new-in-050)) is what made it possible.
 
 ## Why It's Fast
 
@@ -27,7 +27,7 @@ The Android number is a **20× improvement** over the 0.3.x `ZipInputStream`-bas
 - **POSIX `open(O_NOFOLLOW | O_CREAT | O_WRONLY | O_TRUNC | O_CLOEXEC)`** for writes — eliminates the per-file `resolvingSymlinksInPath()` syscall the URL-based path would otherwise pay on every entry. Critical for nested archives where every leaf would otherwise re-stat its ancestors.
 - [**SSZipArchive**](https://github.com/ZipArchive/ZipArchive) is retained ONLY for password-protected paths (read + write), since ZIPFoundation has no AES support.
 
-### Android (0.4.0 NIO migration)
+### Android (0.5.0 NIO migration)
 
 - **`java.util.zip.ZipFile`** for random-access central-directory reads — no inflate to enumerate headers, no TOCTOU window between validate and extract passes (single FD).
 - **`java.nio.file.FileChannel.open(..., NOFOLLOW_LINKS)` + `Channels.newOutputStream(...)`** — typed exceptions (`AccessDeniedException`, `NoSuchFileException`, `FileAlreadyExistsException`), interruptible writes, and proper symlink refusal.
@@ -41,9 +41,9 @@ The Android number is a **20× improvement** over the 0.3.x `ZipInputStream`-bas
 - **Background execution** — extraction runs on native background threads / Swift `Task`s, keeping the UI responsive. iOS also registers a `UIApplication.beginBackgroundTask` so the OS doesn't suspend the app mid-archive.
 - **Transactional**: a mid-stream failure rolls every created file and intermediate directory back, so the destination is never left in a partial-but-looks-complete state.
 
-## What's new in 0.4.0
+## What's new in 0.5.0
 
-| Subsystem | 0.3.x | 0.4.0 |
+| Subsystem | 0.3.x | 0.5.0 |
 |---|---|---|
 | Android engine | `ZipInputStream` (streaming-decode) | `java.util.zip.ZipFile` (random-access central directory) |
 | Android writes | `File` + `FileOutputStream` | `java.nio.file.FileChannel` + `Channels.newOutputStream` (NIO) |

docs/docs/usage/cancellation.md

@@ -22,7 +22,7 @@ task.cancel();
 
 Cancellation is **synchronous** — it happens immediately via JSI with no bridge round-trip. The `await()` promise will reject when a task is cancelled.
 
-**0.4.0 — mid-write cancellation actually fires.** On Android, `cancel()` triggers `Thread.interrupt()` via `runInterruptible`, which unsticks an in-flight `FileChannel` write on the next syscall (not the next chunk boundary). On iOS, `Task.checkCancellation()` runs between every entry, so a cancel between entries halts immediately. In both cases the partial state is then rolled back before the promise rejects — see [Transactional behaviour](./extraction#transactional-behaviour-040).
+**0.5.0 — mid-write cancellation actually fires.** On Android, `cancel()` triggers `Thread.interrupt()` via `runInterruptible`, which unsticks an in-flight `FileChannel` write on the next syscall (not the next chunk boundary). On iOS, `Task.checkCancellation()` runs between every entry, so a cancel between entries halts immediately. In both cases the partial state is then rolled back before the promise rejects — see [Transactional behaviour](./extraction#transactional-behaviour-050).
 
 **`cancel()` before `await()` is a no-op.** If you cancel a task you haven't `await()`'d yet, the next `await()` proceeds normally. This avoids the 0.3-era footgun where a pre-await cancel permanently poisoned the task.
 

docs/docs/usage/compression.md

@@ -67,6 +67,6 @@ if (result.success) {
 | `averageSpeed` | `number` | Average files per second |
 | `totalBytes` | `number` | Total bytes written to the zip file |
 
-:::note Empty directory preservation (0.4.0+)
+:::note Empty directory preservation (0.5.0+)
 Empty placeholder directories in the source (e.g. `cache/`, `logs/today/`) are preserved as trailing-slash entries in the archive, so a zip → unzip round trip keeps them. They do **not** count toward `compressedFiles` / `totalFiles` — those fields use the same files-only semantics as the unzip-side `extractedFiles` / `totalFiles`, so cross-platform round-trip counts match.
 :::

docs/docs/usage/extraction.md

@@ -99,7 +99,7 @@ unzip.extract('/path/to/archive.zip', '/output');
 
 `content://` URIs (returned by Android's Storage Access Framework) are **not** accepted — resolve them to a filesystem path first.
 
-## Transactional behaviour (0.4.0+)
+## Transactional behaviour (0.5.0+)
 
 Extraction is **all-or-nothing**. If anything fails after the first byte is written — a corrupt archive entry, the disk filling up, a write error, or cancellation between entries — the library rolls back every file AND every intermediate directory it created before re-throwing.
 

docs/docs/usage/password.md

@@ -44,10 +44,10 @@ const result = await task.await();
 | Platform | Encryption (write) | Encryption (read) |
 |---|---|---|
 | Android | **AES-256** via [zip4j](https://github.com/srikanth-lingala/zip4j) | AES-256 + traditional PKWARE (zip4j) |
-| iOS (0.4.0+) | **AES-256** via [SSZipArchive](https://github.com/ZipArchive/ZipArchive)'s `aes: true` overload | AES-256 + traditional PKWARE (SSZipArchive) |
+| iOS (0.5.0+) | **AES-256** via [SSZipArchive](https://github.com/ZipArchive/ZipArchive)'s `aes: true` overload | AES-256 + traditional PKWARE (SSZipArchive) |
 
-:::tip 0.4.0 — iOS now writes AES-256
-0.3.x used SSZipArchive's `withPassword:` overload on iOS, which writes **traditional PKWARE encryption** — broken and crackable in minutes with modern tools. 0.4.0 switches to the `aes: true` overload, matching Android's AES-256 strength. Cross-platform password archives now have equivalent crypto strength.
+:::tip 0.5.0 — iOS now writes AES-256
+0.3.x used SSZipArchive's `withPassword:` overload on iOS, which writes **traditional PKWARE encryption** — broken and crackable in minutes with modern tools. 0.5.0 switches to the `aes: true` overload, matching Android's AES-256 strength. Cross-platform password archives now have equivalent crypto strength.
 :::
 
 :::note Cross-platform compatibility

src/specs/Unzip.nitro.ts

@@ -185,7 +185,7 @@ export interface Unzip
    * Create a password-protected ZIP archive from a directory.
    * Uses AES-256 encryption on both Android (via zip4j) and iOS (via
    * SSZipArchive's AES variant). 0.3 used weak PKWARE-traditional
-   * encryption on iOS; 0.4.0 brings cross-platform AES-256 parity.
+   * encryption on iOS; 0.5.0 brings cross-platform AES-256 parity.
    *
    * @param sourcePath - Absolute path to the directory to compress
    * @param destinationZipPath - Absolute path for the output ZIP file