Skip to content

Releases

@checodo/better-auth-normalize@0.2.0

Choose a tag to compare

@github-actions github-actions released this 21 Nov 07:23
6b7b3ba

Minor Changes

  • 2e6b989: First release: email and phone number normalization.

    • emailNormalization() (/email): stores the address an email reaches in user.normalizedEmail (unique): trimmed, lowercased, and the tags (and Gmail's dots) that Gmail, Outlook, iCloud, Proton, and Fastmail ignore removed, or +tags at every domain with subaddressing: "all". A second account for the same inbox is refused on every way of creating a user or changing an email, with better-auth's own answer for an existing email (USER_ALREADY_EXISTS_USE_ANOTHER_EMAIL, or, where better-auth hides existing users, its success-shaped response and onExistingUserSignUp). allowNormalizedSignIn lets people sign in with any form of their address. backfillNormalizedEmails fills existing users a batch at a time and reports inboxes with two accounts. With the audit log, refusals are recorded as normalize.email-alias-refused.
    • phoneNormalization() (/phone): stores every number of better-auth's phoneNumber plugin in E.164 and refuses invalid ones (INVALID_PHONE_NUMBER), with defaultCountry for national numbers.

@checodo/better-auth-blocklist@0.4.0

Choose a tag to compare

@github-actions github-actions released this 21 Nov 07:23
6b7b3ba

Minor Changes

  • 2e6b989: Privacy relays (Firefox Relay, DuckDuckGo, SimpleLogin, addy.io, Proton Pass) are no longer treated as disposable: disposableEmailDomains never contains them (it contained relay.firefox.com). The new privacyRelayDomains list (/lists and /lists/privacy-relay-domains) lets apps that want one account per person block them too. The lists are refreshed from their sources.

@checodo/better-auth-waitlist@0.5.0

Choose a tag to compare

@github-actions github-actions released this 18 Nov 11:53
765926e

Minor Changes

  • 4d87d69: Deleting a user now deletes their waitlist entry, which holds their email address. Before, the entry stayed (marked registered) until an admin deleted it or retention removed it. If you need to keep it, read it in a user.delete.before database hook first.

@checodo/better-auth-security-alerts@0.2.2

Choose a tag to compare

@github-actions github-actions released this 18 Nov 11:53
765926e

Patch Changes

  • 4d87d69: Forgetting a deleted user's devices now shares its code with the other plugins. A failure is logged as [security-alerts] failed to erase the devices of a deleted user; the behavior is unchanged.

@checodo/better-auth-security-alerts@0.2.1

Choose a tag to compare

@github-actions github-actions released this 18 Nov 08:07
f863f8f

Patch Changes

  • 6fb82ef: With newDevice.maxDevices above 100, every known device is now read: the device check and listDevices saw at most 100 of a user's devices.

@checodo/better-auth-referral@0.5.0

Choose a tag to compare

@github-actions github-actions released this 18 Nov 11:53
765926e

Minor Changes

  • 4d87d69: Deleting a user now deletes their referral code, the referrals they made or that brought them, and those referrals' steps and places on every adapter. Before, this relied on foreign keys, so with MongoDB, SQLite without PRAGMA foreign_keys, or a custom adapter the rows stayed. Nothing changes where foreign keys already deleted them.

@checodo/better-auth-referral@0.4.2

Choose a tag to compare

@github-actions github-actions released this 18 Nov 08:07
f863f8f

Patch Changes

  • 6fb82ef: Referral lists now show every completed step: with more than 100 steps on one page of referrals, the rest were left out.

@checodo/better-auth-blocklist@0.3.2

Choose a tag to compare

@github-actions github-actions released this 18 Nov 08:07
f863f8f

Patch Changes

  • 6fb82ef: Security fix: rules stored in the database are now all checked. Only the first 100 rules of each target were read, because better-auth's adapters return at most 100 rows unless told otherwise, so with more than 100 stored rules for a target (emails, usernames, IP addresses...) the newer ones were silently ignored. listRules now also returns every rule.

@checodo/better-auth-audit-log@0.3.1

Choose a tag to compare

@github-actions github-actions released this 18 Nov 08:07
f863f8f

Patch Changes

  • 6fb82ef: verifyAuditChain no longer reports false missing-event problems once the chain has more than 100 links. It read the events of up to 500 links at a time, but got at most 100 back.

@checodo/better-auth-audit-log@0.3.0

Choose a tag to compare

@github-actions github-actions released this 18 Nov 06:29
701f380

Minor Changes

  • 4dbc521: Send audit events to more places with the new destinations option: a SIEM, a log service, or a webhook, each with its own event filter, transform, and batching. Sending runs in the background and is best effort; a failing or slow destination never fails the request. auth.api.flushAuditDestinations() sends waiting batches before shutdown.

    The new @checodo/better-auth-audit-log/destinations entry point has httpDestination (JSON or NDJSON, optional Standard Webhooks signature, never follows redirects) and consoleDestination.

    A custom storage now only needs write: without read, listEvents answers READ_NOT_SUPPORTED (501); without deleteOlderThan, retention is refused at startup and deleteExpiredAuditEvents answers DELETE_NOT_SUPPORTED (501). Existing storages keep working.

  • 46134cf: Export audit events and verify the hash chain over HTTP, for admins.

    • GET /audit-log/export (auth.api.exportAuditEvents): NDJSON or CSV, newest first, with the same filters as listEvents. Up to 10,000 events per request; the x-next-cursor response header continues the export, unaffected by new events. CSV cells that a spreadsheet would run as a formula get a leading '.
    • POST /audit-log/verify-chain (auth.api.verifyAuditChain): now also reachable over HTTP, at most 10,000 links per request. The new afterSequence and limit options check the chain in parts; the result's new nextSequence continues the check.
    • Both are admins only over HTTP (new error codes YOU_ARE_NOT_ALLOWED_TO_EXPORT_EVENTS, YOU_ARE_NOT_ALLOWED_TO_VERIFY_THE_CHAIN, INVALID_CURSOR) and rate limited to 10 requests a minute. Calls from server code without headers need no session, as before.