Prepare 1.0.0 release

Author: eldryoth

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## 1.0.0-alpha.0 - Unreleased
+## 1.0.0 - 2026-05-19
 
 - Started the stable API and security-contract freeze candidate after the
   `0.12.0` stabilization release.

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "base64-ng"
-version = "1.0.0-alpha.0"
+version = "1.0.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.12.0`. The development branch is
-`1.0.0-alpha.0`.
+The current public release is `1.0.0`.
 
 Implemented now:
 
@@ -48,8 +47,8 @@ Implemented now:
 Planned behind admission evidence:
 
 - Admitted AVX2, AVX-512, SSSE3/SSE4.1, ARM NEON, and wasm `simd128`
-  fast paths after the SIMD admission evidence is complete. Current `1.0`
-  development remains scalar-only unless that full evidence package lands.
+  fast paths after the SIMD admission evidence is complete. The `1.0.0`
+  release remains scalar-only.
 - Async streaming wrappers only after the `tokio` feature passes the
   dependency and cancellation-safety admission bar in [docs/ASYNC.md](docs/ASYNC.md).
 - Optional `serde` or `bytes` integration only if a concrete use case clears
@@ -82,7 +81,7 @@ and CWE mapping lives in [docs/SECURITY_CONTROLS.md](docs/SECURITY_CONTROLS.md).
 
 ```toml
 [dependencies]
-base64-ng = "1.0.0-alpha.0"
+base64-ng = "1.0.0"
 ```
 
 The crate is dual-licensed:
@@ -109,7 +108,7 @@ Disable defaults for embedded or freestanding use:
 
 ```toml
 [dependencies]
-base64-ng = { version = "1.0.0-alpha.0", default-features = false }
+base64-ng = { version = "1.0.0", default-features = false }
 ```
 
 ## Example

README.md

@@ -299,8 +299,8 @@ buffer types intentionally do not implement `PartialEq`/`==`: the explicit
 method name is part of the security contract because this helper is best-effort
 and not a formal cryptographic comparison primitive.
 
-The old `constant_time_eq` method name was removed during the `1.0.0-alpha`
-window. Use `constant_time_eq_public_len` so the public-length contract remains
+The old `constant_time_eq` method name was removed before `1.0.0`. Use
+`constant_time_eq_public_len` so the public-length contract remains
 visible at the call site.
 
 Length mismatch returns immediately. Treat buffer length, the selected buffer

docs/CONSTANT_TIME.md

@@ -53,11 +53,11 @@ Review focus:
 
 ## Current Release Position
 
-For the current `1.0.0-alpha.0` development branch:
+For the `1.0.0` release:
 
 - Assembly evidence generation is release-gated.
-- Manual review is required before a stable release that strengthens ct
-  wording.
+- Manual review is required before any future release that strengthens ct
+  wording beyond "constant-time-oriented".
 - The public documentation continues to use "constant-time-oriented" wording.
 - No formally verified cryptographic constant-time guarantee is claimed.
 

docs/CT_ASM_REVIEW.md

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

docs/MIGRATION.md

@@ -250,14 +250,12 @@ The crate is feature-rich enough for normal Base64 use, and the remaining
 `v0.11`, and `v0.12` lines completed the intended audit preparation,
 verification hardening, and stabilization rehearsal work.
 
-The current honest path is:
-
-- `v1.0.0-alpha.0`: freeze candidate for pentest, CI, and downstream review.
-  This version should change only for release blockers, documentation
-  corrections, or evidence-policy fixes.
-- `v1.0.0`: stable API and security-contract release after the alpha candidate
-  has clean local release evidence, clean CI, and clean external pentest
-  results.
+The current release path is:
+
+- `v1.0.0`: stable API and security-contract release after the freeze
+  candidate had clean local release evidence, clean CI, and clean external
+  pentest results. This line should change only for release blockers,
+  documentation corrections, or evidence-policy fixes before tagging.
 - `1.0.x`: maintenance and assurance releases. Kani proof execution remains a
   high-priority `1.0.x` follow-up once Kani supports the pinned Rust toolchain.
 
@@ -545,7 +543,7 @@ cryptographic behavior until compatible verifier evidence exists.
 ### v1.0
 
 - No unresolved `v0.10`, `v0.11`, or `v0.12` release-candidate blockers.
-- `1.0.0-alpha.0` pentest, GitHub CI, and local release evidence must be clean
+- `1.0.0` pentest, GitHub CI, and local release evidence must be clean
   before the stable `v1.0.0` tag.
 - Kani proofs are not required for the initial stable release if the documented
   `v1.0` verifier exception remains accepted and the replacement evidence is

docs/PLAN.md

@@ -26,8 +26,8 @@ generated assembly review, including LTO symbol-presence checks for the helper,
 but no formal cryptographic constant-time comparison guarantee is claimed.
 High-assurance applications that can admit a comparison dependency should use a
 reviewed primitive such as `subtle` at the protocol boundary. The shorter
-`constant_time_eq` name was removed during the `1.0.0-alpha` window so the
-public-length comparison contract stays visible at call sites.
+`constant_time_eq` name was removed before `1.0.0` so the public-length
+comparison contract stays visible at call sites.
 
 ## Caller Responsibilities
 

docs/SECURITY_CONTROLS.md

@@ -1,8 +1,8 @@
 # SIMD Admission Policy
 
-`base64-ng` is intentionally scalar-only in the `1.0.0-alpha.0` development
-branch unless a complete SIMD admission evidence package lands in the same
-release series. The crate uses `#![deny(unsafe_code)]` and permits reviewed
+`base64-ng` is intentionally scalar-only in the `1.0.0` release. Future SIMD
+dispatch remains gated unless a complete SIMD admission evidence package lands
+in a later release series. The crate uses `#![deny(unsafe_code)]` and permits reviewed
 `allow(unsafe_code)` exceptions only for audited cleanup, CT barrier, validated
 secret conversion helpers in `src/lib.rs`, and the private `src/simd.rs`
 boundary. The `simd` feature remains reserved until architecture-specific code