1.0 readiness
A 1.0 release requires all of the following.
Current release: 0.10.4.
Criteria
| Item | Status |
|---|---|
| Workspace quality gate | Complete: 341 tests, no_std, MSRV, docs, package and semver |
| Conformance corpus | Complete for the current corpus: 80 cases and 20 profiles |
| Manual performance record | Complete on kbench |
| Sustained fuzzing | In progress: 1 of 4 scheduled runs |
| External adopter | Complete: alint, a separate public repository |
| CLI and library contracts | Frozen |
Required evidence
- Re-run the release gate from quality.md.
- Record an idle-host performance run and compare it with performance.md and benchmark-dashboard.md.
- Confirm four consecutive scheduled fuzz runs for all five targets after the last parser, edit, encoding, resolution or formatting change. The first run passed on 2026-10-26; the next dates are 2026-11-02, 2026-11-09 and 2026-11-16.
- Confirm at least one external project uses a published adotenv crate, with the maintainer’s confirmation and the version and features used.
- Verify the tag, crates.io versions, docs.rs builds and GitHub Release.
External adopter
- Project:
asamarts/alint, a separate public repository. - Adotenv version: 0.10.4, default features.
- Use: literal dotenv parsing, diagnostics, spans and native verified edits in alint-core.
- Compatibility finding: upgrading from adotenv 0.2.1 required no alint source changes.
- Verification: 887 alint-core tests and 270 alint CLI tests pass; Cross-Platform CI and the quality jobs pass.
Fuzz rule
A manual fuzz run does not count toward the four scheduled runs. A skipped, cancelled or failed run does not count. A fuzz-relevant code change restarts the count.
Adopter rule
An adopter must be outside this repository and must use a published crate. Downloads, stars and issue comments do not qualify. Public attribution is optional; the maintainer confirmation must be recorded.