v4.0.1

4.0.1 (2025-02-25)

Bug Fixes

• ensured that generateTOTP converts the digits and period params into numbers. (#25) (33d8db9)

v4.0.0

4.0.0 (2025-02-24)

Bug Fixes

• revert all commits back to bab1ccc (dc62fc1)

BREAKING CHANGES

• Removes compatibilities added up to v3.0.0

v3.1.0

3.1.0 (2025-02-17)

Features

• Allow to generate TOTP codes up to 20 character long (#24) (2242335)

v3.0.2

3.0.2 (2025-02-15)

Bug Fixes

• prevent certain offset values to address out of hashBytes (#23) (3bf1701)

v3.0.1

3.0.1 (2025-02-15)

Bug Fixes

• Stay compatible with the authenticator apps (#22) (09f5f48)

v3.0.0

3.0.0 (2025-02-14)

Bug Fixes

• add optional chaining for algorithm name in TOTP URI generation (746f615)
• normalize algorithm name for TOTP Auth URI generation (e5645d0)
• simplify algorithm name extraction in TOTP URI generation (bab1ccc)

BREAKING CHANGES

• Technically, we are changing the algorithm param that is returned from getTOTPAuthUri and that could be a breaking change for some people, but it shouldn't be a breaking change for most (any). So go ahead and update this without concern.

v2.2.0

2.2.0 (2025-02-14)

Features

• improve HOTP generation for longer OTPs (adc780e)

v2.1.1

2.1.1 (2025-01-19)

Bug Fixes

• add missing repository.url value to create new release (#19) (5667722)

v2.0.0

2.0.0 (2024-09-08)

Features

• Convert Buffer and node crypto to web apis (#11) (e4b8a20)

BREAKING CHANGES

• exported functions are now async
• the name of the algorithm option has changed from SHA1 / SHA256 / etc. to SHA-1, SHA-256, etc.

NOTE: if you're looking at upgrading to this with the Epic Stack, you'll need to migrate your existing verifications. Here's some SQL you can use:

-- Update SHA1 to SHA-1
UPDATE "Verification"
SET "algorithm" = 'SHA-1'
WHERE "algorithm" = 'SHA1';

-- Update SHA256 to SHA-256
UPDATE "Verification"
SET "algorithm" = 'SHA-256'
WHERE "algorithm" = 'SHA256';

-- Update SHA512 to SHA-512
UPDATE "Verification"
SET "algorithm" = 'SHA-512'
WHERE "algorithm" = 'SHA512';

You could add this as a migration script, or run it as a one-time thing.

v1.1.3

1.1.3 (2024-08-29)

Bug Fixes

• use new base 32 encode and decode (#9) (dc6d694), closes #8