lukk

Appearance

Upgrading ​

Both halves of lukk are pre-1.0 (0.x). Per SemVer §4, a minor bump (0.x.0) may carry a breaking change; a patch bump (0.x.y) never does. The 1.0 releases will mark API/schema stability and end this cadence.

Each repo keeps a version-specific UPGRADE.md — the authoritative, "you may need to do something" subset of its changelog, organized highest-version-first with High / Medium / Low impact tags. Read it (and the changelog) before bumping:

Ground rules ​

  • Pin an exact version. Don't float ^ on a 0.x dependency you can't retest.
  • Upgrade the server first. lukk's HTTP contract is the source of truth; the client only speaks it. When a server change needs a matching client change, its UPGRADE.md entry says so.
  • Nothing auto-applies. lukk's migrations are publish-only and its behavior is config-gated — an upgrade only touches what you've opted into.
  • Run your tests after bumping, then read the entries at or below your target version.

Highest-impact change right now ​

WARNING

lukk 0.6.0 adds a guard column to passkeys and turns account deletion on by default.

The column is folded into the existing passkeys migration, so a fresh install needs no action and a single-guard install is unaffected (the column stays null and no query names it). An install that already ran that migration and uses multiple guards must add the column and backfill it — until it does, lukk:prune deliberately sweeps no passkeys at all rather than risk deleting a credential it cannot attribute.

Removing a guard needs the opposite cleanup, and it fails open: rows still stamped with the departed guard's name become visible to the default guard, and for passkeys that lookup is the authentication decision. Delete or re-home them first.

features.account_deletion defaults to true, so upgrading adds an irreversible route (DELETE /auth/account). Turn it off if deletion is owned elsewhere. Both directions and the SQL are in lukk UPGRADE.md.

NOTE

lukk 0.4.0 added a guard column to refresh_tokens on the same terms — folded into the core migration, no action for fresh or single-guard installs, and the identical backfill caveat in both directions. See lukk UPGRADE.md.

lukk-js has shipped no breaking changes yet — every release has been additive.