Prepare 0.5.0 release

Author: eldryoth

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## 0.5.0-alpha.0 - Unreleased
+## 0.5.0 - 2026-05-14
 
 - Started the next development cycle after the `0.4.1` release.
 - Added AVX-512 VBMI candidate detection to runtime backend reports while

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "base64-ng"
-version = "0.5.0-alpha.0"
+version = "0.5.0"
 edition = "2024"
 rust-version = "1.95"
 license = "MIT OR Apache-2.0"

Cargo.toml

@@ -6,8 +6,7 @@ The crate starts conservative: a small scalar implementation, strict RFC 4648 be
 
 ## Current Status
 
-The current public release is `0.4.1`. The `main` branch now tracks the
-`0.5.0-alpha.0` development cycle.
+The current public release is `0.5.0`.
 
 Implemented now:
 
@@ -42,7 +41,7 @@ Planned behind admission evidence:
 
 ```toml
 [dependencies]
-base64-ng = "0.4.1"
+base64-ng = "0.5.0"
 ```
 
 The crate is dual-licensed:
@@ -67,7 +66,7 @@ Disable defaults for embedded or freestanding use:
 
 ```toml
 [dependencies]
-base64-ng = { version = "0.4.1", default-features = false }
+base64-ng = { version = "0.5.0", default-features = false }
 ```
 
 ## Example

README.md

@@ -19,14 +19,14 @@ After:
 
 ```toml
 [dependencies]
-base64-ng = "0.4.1"
+base64-ng = "0.5.0"
 ```
 
 For embedded or freestanding use:
 
 ```toml
 [dependencies]
-base64-ng = { version = "0.4.1", default-features = false }
+base64-ng = { version = "0.5.0", default-features = false }
 ```
 
 ## Engine Mapping
@@ -152,7 +152,7 @@ Enable the `stream` feature for `std::io` wrappers:
 
 ```toml
 [dependencies]
-base64-ng = { version = "0.4.1", features = ["stream"] }
+base64-ng = { version = "0.5.0", features = ["stream"] }
 ```
 
 ```rust

docs/MIGRATION.md

@@ -228,6 +228,47 @@ Phase 3:
 - Release-gate hardening for packaged evidence, reserved feature placeholders,
   unsafe/SIMD boundary validation, and cross-target SIMD feature bundles.
 
+### v0.6
+
+- Expand Kani proof coverage for length helpers, in-place decode bounds, and
+  selected scalar decoder invariants when Kani supports the pinned Rust
+  toolchain.
+- Strengthen Miri coverage for scalar, in-place, clear-tail, and stream state
+  machine behavior that Miri can execute practically.
+- Add a documented constant-time verification plan for the `ct` module,
+  including generated-code review requirements before making cryptographic
+  constant-time claims.
+- Stabilize fuzz corpus handling and document which corpus inputs are accepted
+  into the repository.
+
+### v0.7
+
+- Replace inactive SIMD encode prototypes with real candidate implementations
+  only when scalar differential tests, fuzz evidence, target-feature checks,
+  unsafe inventory updates, and benchmark evidence are complete.
+- Keep scalar as the default fallback and require runtime backend policy tests
+  for every admitted accelerated backend.
+- Publish per-architecture benchmark evidence for any performance claim,
+  including CPU, OS, Rust version, command, and raw output.
+
+### v0.8
+
+- Consider admitting async streaming wrappers only after `docs/ASYNC.md`
+  requirements are met, including dependency review, cancellation behavior,
+  drop cleanup behavior, chunk-boundary tests, and release evidence with the
+  async feature enabled.
+- If async remains unjustified, keep `tokio` inert and spend this milestone on
+  stream ergonomics, documentation, and additional framed-protocol tests.
+
+### v0.9
+
+- Release-candidate hardening for `v1.0`: API audit, documentation audit,
+  migration guide refresh, fuzz corpus review, benchmark review, and release
+  evidence rehearsal.
+- Decide whether constant-time decode is formally guaranteed with supporting
+  evidence or explicitly documented as constant-time-oriented only.
+- Freeze dependency policy and feature admission rules for `v1.0`.
+
 ### v1.0
 
 - Kani proofs complete for scalar in-place decode.

docs/PLAN.md

@@ -1,7 +1,6 @@
 # SIMD Admission Policy
 
-`base64-ng` is intentionally scalar-only in the `0.5.0-alpha.0` development
-cycle. The crate uses
+`base64-ng` is intentionally scalar-only in the `0.5.0` release. The crate uses
 `#![deny(unsafe_code)]` and permits `allow(unsafe_code)` only in the private
 `src/simd.rs` boundary. The `simd` feature remains reserved until
 architecture-specific code has enough evidence to justify enabling it.

docs/SIMD.md

@@ -9,7 +9,7 @@ cargo-fuzz = true
 
 [dependencies]
 base64 = "0.22.1"
-base64-ng = { path = "..", version = "0.5.0-alpha.0", features = ["alloc", "std", "stream"] }
+base64-ng = { path = "..", version = "0.5.0", features = ["alloc", "std", "stream"] }
 libfuzzer-sys = "0.4"
 
 [[bin]]