Skip to content

chore(deps): bump otplib from 13.4.1 to 13.5.0 - #3672

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/otplib-13.5.0
Open

chore(deps): bump otplib from 13.4.1 to 13.5.0#3672
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/otplib-13.5.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 25, 2026

Copy link
Copy Markdown

Bumps otplib from 13.4.1 to 13.5.0.

Release notes

Sourced from otplib's releases.

v13.5.0

What's Changed

Full Changelog: yeojz/otplib@v13.4.1...v13.5.0


Important behaviour change in this bugfix release.

[!NOTE] This is a bugfix release but has potentially breaking behaviour for library users passing invalid inputs (which is more likely in non-TypeScript or loosely-typed environments).

This release (#874) makes hash algorithm validation consistent and strict across all crypto plugins. Previously, an unrecognised algorithm string was handled differently by each plugin:

input noble node web
'SHA1' silently computed SHA-512 worked (OpenSSL alias tolerance) threw a raw TypeError
'totally-bogus' silently computed SHA-512 threw threw

All three now reject anything outside sha1/sha256/sha512 (case-insensitive, single-separator aliases like SHA-1 or sha_256 accepted) by throwing the new AlgorithmUnsupportedError, 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 as algorithm is 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

  • Change algorithm to sha512,
  • or re-enroll the affected accounts.

See "Existing enrollments stopped verifying after an upgrade" for details.

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [otplib](https://github.com/yeojz/otplib/tree/HEAD/packages/otplib) from 13.4.1 to 13.5.0.
- [Release notes](https://github.com/yeojz/otplib/releases)
- [Commits](https://github.com/yeojz/otplib/commits/v13.5.0/packages/otplib)

---
updated-dependencies:
- dependency-name: otplib
  dependency-version: 13.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants