Skip to content

keychain: drop "v2" and legacy-migration wording - #686

Merged
glitch003 merged 1 commit into
mainfrom
glitch003/remove-keychain-v2-versioning
Sep 17, 2026
Merged

glitch003 merged 1 commit into
mainfrom
glitch003/remove-keychain-v2-versioning

Conversation

@clawdbot-glitch003

Copy link
Copy Markdown
Collaborator

Keychain is prelaunch with no users, so there is no v1 and nothing to be backwards compatible with. This removes the "v2" label from SKILL.md, README, AGENTS.md, SECURITY.md, ADVERSARIAL_REVIEW.md, the SDK README and the CI workflow name, and rewrites the README paragraph about migrating from a "legacy" service.

Deliberately unchanged:

  • version: 2.0.5 in SKILL.md and the npm package version: npm versions cannot go backwards and 2.0.x is already published.
  • Protocol domain-separation tags (lit-keychain/v2, lit-keychain/receipt/v2, ...): baked into the action bytes, so renaming them changes every template hash and encryption key.
  • The comment in migration 20260911000001: sqlx checksums migration files, so editing it would break migrate run on the existing dev database.

🤖 Generated with Claude Code

…h with no prior version

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@clawdbot-glitch003
clawdbot-glitch003 requested a review from a team September 17, 2026 21:39
@glitch003
glitch003 merged commit 9c42596 into main Sep 17, 2026
13 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants