Update dependency otplib to v13 - #182
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/otplib-13.x
branch
2 times, most recently
from
March 19, 2026 17:33
74da55c to
97f7a02
Compare
renovate
Bot
force-pushed
the
renovate/otplib-13.x
branch
2 times, most recently
from
April 1, 2026 20:05
b8f351c to
e4849d4
Compare
renovate
Bot
force-pushed
the
renovate/otplib-13.x
branch
from
April 8, 2026 21:00
e4849d4 to
0032172
Compare
renovate
Bot
force-pushed
the
renovate/otplib-13.x
branch
from
April 29, 2026 13:48
0032172 to
582d040
Compare
renovate
Bot
force-pushed
the
renovate/otplib-13.x
branch
2 times, most recently
from
May 18, 2026 11:39
9a1a1c8 to
09f0940
Compare
renovate
Bot
force-pushed
the
renovate/otplib-13.x
branch
from
June 11, 2026 17:11
09f0940 to
5cf6cb3
Compare
renovate
Bot
force-pushed
the
renovate/otplib-13.x
branch
3 times, most recently
from
July 16, 2026 14:56
60d5c63 to
df0ec65
Compare
renovate
Bot
force-pushed
the
renovate/otplib-13.x
branch
from
July 30, 2026 18:58
df0ec65 to
6b5392a
Compare
renovate
Bot
force-pushed
the
renovate/otplib-13.x
branch
2 times, most recently
from
August 14, 2026 17:08
19a4815 to
e24b424
Compare
renovate
Bot
force-pushed
the
renovate/otplib-13.x
branch
2 times, most recently
from
August 26, 2026 12:00
6f2532c to
2b773f4
Compare
renovate
Bot
force-pushed
the
renovate/otplib-13.x
branch
from
September 2, 2026 19:36
2b773f4 to
f031571
Compare
renovate
Bot
force-pushed
the
renovate/otplib-13.x
branch
from
September 3, 2026 19:29
f031571 to
4bc095d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^12.0.1→^13.0.0Release Notes
yeojz/otplib (otplib)
v13.5.0Compare Source
What's Changed
Full Changelog: yeojz/otplib@v13.4.1...v13.5.0
Important behaviour change in this bugfix release.
This release (#874) makes hash algorithm validation consistent and strict across all crypto plugins. Previously, an unrecognised
algorithmstring was handled differently by each plugin:'SHA1'TypeError'totally-bogus'All three now reject anything outside
sha1/sha256/sha512(case-insensitive, single-separator aliases likeSHA-1orsha_256accepted) by throwing the newAlgorithmUnsupportedError, instead of silently substituting a different digest.A library dependents passing a correctly-spelled algorithm name (
'sha1','SHA1','sha-256', etc.) sees no change other than clearer, stricter errors on genuinely invalid input. In TypeScript-strict environments this is mostly moot asalgorithmis typed as 'sha1' | 'sha256' | 'sha512', so a hardcoded typo like 'SHA1' won't compile. It can still surface if the value comes from outside the type system (e.g. JSON.parse, process.env, or an as HashAlgorithm cast).If you were relying on noble's old silent fallback to SHA-512 for a misspelled or unrecognised algorithm string, tokens generated/verified that way will stop matching after upgrading with no error on the old side, just tokens that quietly stop verifying.
To recover
sha512,See "Existing enrollments stopped verifying after an upgrade" for details.
v13.4.1Compare Source
What's Changed
New Contributors
Full Changelog: yeojz/otplib@v13.4.0...v13.4.1
v13.4.0Compare Source
What's Changed
New Contributors
Full Changelog: yeojz/otplib@v13.3.0...v13.4.0
v13.3.0Compare Source
What's Changed
New Contributors
Full Changelog: yeojz/otplib@v13.2.1...v13.3.0
v13.2.1Compare Source
What's Changed
Full Changelog: yeojz/otplib@v13.2.0...v13.2.1
v13.2.0Compare Source
What's Changed
Callout
[number, number]instead of the previousnumber[]. There was an erroneous logic from the intended documentation/usage . Please double check your HOTP tolerance if it's used.Full Changelog: yeojz/otplib@v13.1.1...v13.2.0
v13.1.1Compare Source
What's Changed
Full Changelog: yeojz/otplib@v13.1.0...v13.1.1
v13.1.0Compare Source
What's Changed
Full Changelog: yeojz/otplib@v13.0.2...v13.1.0
v13.0.2What's Changed
Full Changelog: yeojz/otplib@v13.0.0...v13.0.2
v13.0.0Compare Source
What's Changed
Full Changelog: yeojz/otplib@v12.0.1...v13.0.0
Related Issues
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.