Skip to content

docs(migration): bump uselesskey 0.6.0 references to 0.7.0 #574

Description

@EffortlessSteven

@

Summary

docs/how-to/migration.md still tells users to install uselesskey = "0.6.0" and the title/lead/checklist all reference 0.6.0. With v0.7.0 published, the migration guide is the primary external-user landing page for adoption and is now version-stale. New users following the guide will pin an outdated minor.

Evidence

grep -n "0\.6\.0" docs/how-to/migration.md:

1:# Migrating to `uselesskey` 0.6.0: deterministic crypto fixtures without committed blobs
3:This guide shows how to replace committed PEM/DER/JWK/token blobs with runtime-generated fixtures using `uselesskey` **0.6.0**.
21:uselesskey = { version = "0.6.0", default-features = false, features = ["rsa", "jwk"] }
29:uselesskey = { version = "0.6.0", default-features = false, features = ["token"] }
35:uselesskey = { version = "0.6.0", default-features = false, features = ["x509"] }
36:uselesskey-rustls = { version = "0.6.0" }
42:uselesskey = { version = "0.6.0", default-features = false, features = ["rsa", "hmac", "jwk"] }
43:uselesskey-jsonwebtoken = { version = "0.6.0" }
44:uselesskey-jose-openid = { version = "0.6.0" }
176:1. Add `uselesskey` 0.6.0 to `[dev-dependencies]`

(Other 0.6.0 hits in the repo are legitimate — CHANGELOG.md history, docs/explanation/roadmap.md "Shipped" section, docs/release/v0.7.0-category-notes.md notes-start-tag v0.6.0, docs/release/evidence-matrix-v0.7.0.md baseline, docs/explanation/roadmap-followups-0251.md historical milestone.)

Plan

  1. Update title (line 1) and lead paragraph (line 3) from 0.6.0 to 0.7.0.
  2. Update every version = "0.6.0" in dependency snippets (lines 21, 29, 35, 36, 42, 43, 44) to "0.7.0".
  3. Update checklist step (line 176) from 0.6.0 to 0.7.0.
  4. Run cargo xtask docs-sync --check (snippets are dependency-snippets, so docs-sync may regenerate them; reconcile if so).
  5. Optional: review crates/uselesskey/README.md and root README.md for the same drift while in the area.

Acceptance criteria

  • rg "0\.6\.0" docs/how-to/migration.md returns no matches.
  • cargo xtask docs-sync --check exits 0.
  • The migration title/lead match the latest published minor (0.7.0).

Effort estimate

small — single-file find/replace plus a docs-sync verification.

Not in scope

  • Not a code change; no API/behavior changes.
  • Not touching CHANGELOG.md, roadmap.md, evidence-matrix-v0.7.0.md, or release notes — those legitimately reference 0.6.0 as historical context or as a release-notes baseline.
  • Not a broader version-reference audit across the whole repo (file this separately if drift is found elsewhere).
    @

Metadata

Metadata

Assignees

No one assigned

    Labels

    docsDocumentation and docs-sync related work

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions