Release base64-ng 0.6.0

Author: eldryoth

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## 0.6.0-alpha.0 - Unreleased
+## 0.6.0 - 2026-05-14
 
 - Started the next development cycle after the `0.5.0` release.
 - Added no-alloc validation-only APIs for strict and legacy profiles:

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "base64-ng"
-version = "0.6.0-alpha.0"
+version = "0.6.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.5.0`. The development branch is
-`0.6.0-alpha.0`.
+The current public release is `0.6.0`.
 
 Implemented now:
 
@@ -72,7 +71,7 @@ and CWE mapping lives in [docs/SECURITY_CONTROLS.md](docs/SECURITY_CONTROLS.md).
 
 ```toml
 [dependencies]
-base64-ng = "0.5.0"
+base64-ng = "0.6.0"
 ```
 
 The crate is dual-licensed:
@@ -97,7 +96,7 @@ Disable defaults for embedded or freestanding use:
 
 ```toml
 [dependencies]
-base64-ng = { version = "0.5.0", default-features = false }
+base64-ng = { version = "0.6.0", default-features = false }
 ```
 
 ## Example

README.md

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

docs/MIGRATION.md

@@ -1,6 +1,6 @@
 # SIMD Admission Policy
 
-`base64-ng` is intentionally scalar-only in the `0.5.0` release. The crate uses
+`base64-ng` is intentionally scalar-only in the `0.6.0` release. The crate uses
 `#![deny(unsafe_code)]` and permits reviewed `allow(unsafe_code)` exceptions
 only for the volatile wipe helper in `src/lib.rs` and the private `src/simd.rs`
 boundary. The `simd` feature remains reserved until architecture-specific code

docs/SIMD.md

@@ -1,8 +1,8 @@
 # Trust Dashboard
 
 This dashboard is a concise adoption checklist for security-sensitive users.
-It describes the current development branch and should be refreshed before
-each stable release.
+It describes the current release posture and should be refreshed before each
+stable release.
 
 | Area | Current Status | Evidence |
 | --- | --- | --- |
@@ -16,7 +16,7 @@ each stable release.
 | SIMD status | Reserved prototypes only; no accelerated backend admitted | `docs/SIMD.md` |
 | Strict decoding | Default behavior rejects whitespace, mixed alphabets, malformed padding, and non-canonical trailing bits | integration tests |
 | Legacy compatibility | Explicit opt-in APIs only | `decode_slice_legacy`, `validate_legacy` |
-| Constant-time API | Constant-time-oriented scalar decode exists; no formal cryptographic constant-time guarantee | `docs/CONSTANT_TIME.md` |
+| Constant-time API | Constant-time-oriented scalar validation/decode exists; no formal cryptographic constant-time guarantee | `docs/CONSTANT_TIME.md` |
 | Cleanup posture | Clear-tail APIs, stream cleanup, `EncodedBuffer`, and `SecretBuffer` provide best-effort initialized-byte cleanup | `SECURITY.md` |
 | Fuzzing | Isolated `cargo-fuzz` harnesses outside the published dependency graph | `fuzz/`, `docs/RELEASE_EVIDENCE.md` |
 | Miri | Release gate runs Miri when nightly Miri is installed | `scripts/stable_release_gate.sh` |

docs/TRUST.md

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