From c30345150b75e7424132764538561c202d988a76 Mon Sep 17 00:00:00 2001 From: Michael Gilardi <11632652+mgilardi@users.noreply.github.com> Date: Mon, 16 Nov 2026 20:42:39 -0700 Subject: [PATCH] Say which version is on npm in the README and changelog The status line and changelog headings still said the package wasn't published, after the release went out. They now give the published version and date, checked against npm and the published commit, and say what's on main but not released yet. Docs only. Co-Authored-By: Claude Opus 5.5 --- CHANGELOG.md | 6 ++++-- README.md | 2 +- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 5092fe7..204f405 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -9,7 +9,9 @@ Tested: 4 new tests (50 in all), on in-memory MongoDB with made-up accounts only, not a copy of any site's data: null and empty-secret records with a pending setup and an email block are merged (secret, enabled date, last step; email block and pending kept; no recovery codes; old group gone; two-step on; sign-in works; rerun is a no-op); a record left by `turnOff` and one left by `resetFor` are not merged, keep the old field, no secret and no recovery, and are listed in `needsReview` (also on a rerun); same and different secrets are kept and the different one reported; an account with no record moves as before. Not tested: a real site database, a merge write that loses a race, or a mutation check of the new guard. -## 0.1.1 (unreleased) +## 0.1.0 (2026-11-13) + +Published as 0.1.0 together with the first version below. 0.1.1 was never released on its own. - `onEvent` gets a copy of the request without the entered code, the remember value, the headers (cookies, tokens and the client address) or the body. The raw request used to reach it, so a site logging `event.req` could have stored a code (found by the 2026-11-10 test self-audit). `payload` and the translation helpers stay on the copy but aren't enumerable, so a logger walking it never reaches the app's secret. The actor of an event is `event.user`: during a sign-in, `req.user` is whoever the request already had. @@ -20,7 +22,7 @@ Tested: 4 new tests (50 in all), on in-memory MongoDB with made-up accounts only Tested: 5 new tests (29 in all), including a reset racing a write that would keep the old secret, and old sessions written back after a reset (refused at request and at refresh). A security read approved 85b901f and found the session race in da6bfe2; both are fixed here. A mutation check shows each part of the reset fails one of the reset's own tests when removed: the cleared secret and recovery codes, the version guard, the cleared tries, ending sessions, the kept email-code block, and both window bounds. Not yet used on a site. -## 0.1.0 (unreleased) +### First version First version, as `payload-plugin-mfa` (renamed from payload-plugin-two-step by the owner, 2026-11-10), extracted from the first site's own two-step sign-in, with the decisions in `docs/adr/0001-design.md` (including the pre-publish read): factors, use-once codes with a race guard, per-account limits with keys built inside, the required rule at sign-in, refresh and every request, per-session expiry, remembered browsers, email codes blocked after a reset, step-up `verify`, and the login endpoint. diff --git a/README.md b/README.md index 112fa27..bc91a4a 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ MFA for Payload (two-step sign-in): an authenticator code after the password, with emailed and recovery codes as backups, each used once, limited per account, and required by a rule you set. -**Status:** early, 0.1.0, not on npm yet. 46 tests pass against a real Payload 3.92 with an in-memory MongoDB, covering every factor, replays, the limits (including 40 tries at once), remembered browsers, per-session expiry, the required rule, the login endpoint, and races with Payload's own sign-in (a sign-in begun earlier can't undo two-step or reuse a code). It's extracted from the version a live site runs, but this package itself isn't in use on any site yet, and it has no screens of its own: your site builds the sign-in and settings pages. +**Status:** early. 0.1.0 is on npm (2026-11-13). The `moveLegacyState` fixes under Unreleased in the changelog are on main, not released yet. 46 tests pass against a real Payload 3.92 with an in-memory MongoDB, covering every factor, replays, the limits (including 40 tries at once), remembered browsers, per-session expiry, the required rule, the login endpoint, and races with Payload's own sign-in (a sign-in begun earlier can't undo two-step or reuse a code). It's extracted from the version a live site runs, but this package itself isn't in use on any site yet, and it has no screens of its own: your site builds the sign-in and settings pages. ## What it does