Skip to content

fix(deps): update dependency @noble/ciphers to v2#326

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/noble-ciphers-2.x
Open

fix(deps): update dependency @noble/ciphers to v2#326
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/noble-ciphers-2.x

Conversation

@renovate

@renovate renovate Bot commented Aug 25, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@noble/ciphers (source) ^1.0.0^2.0.0 age confidence

Release Notes

paulmillr/noble-ciphers (@​noble/ciphers)

v2.2.0

Compare Source

  • March 2026 self-audit (all files): no major issues found
    • Audited for spec compliance and security
    • Fix: ctr from webcrypto submodule used wrong counter wrapping
    • Fix: MAC no longer corrupts oversized outputs
    • Align CMAC API to other MACs
  • Fix all Byte Array types, to ensure proper work in both TypeScript 5.6 & TypeScript 5.9+
    • TS 5.6 has Uint8Array, while TS 5.9+ made it generic Uint8Array<ArrayBuffer>
    • This creates incompatibility of code between versions
    • Previously, it was hard to use and constantly emitted errors similar to TS2345
    • See typescript#62240 for more context
  • Fix compilation issues on TypeScript v6
  • Zeroization improvements by @​ChALkeR in #​67, #​68
  • Make package Big Endian friendly. All tests pass on s390x
  • Improve tree-shaking, reduce bundle sizes
  • Add massive amounts of documentation everywhere

Full Changelog: paulmillr/noble-ciphers@2.1.1...2.2.0

v2.1.1

Compare Source

  • Implement AES-SIV by @​overheadhunter in #​62
    • AES-SIV (RFC 5297) is different from AES-GCM-SIV (RFC 8452)
    • Deprecate old siv export in aes.js because it was an alias to gcmsiv
  • Publish provenance statement, missed in 2.0.1 due to GitHub bugs

New Contributors

Full Changelog: paulmillr/noble-ciphers@2.0.1...2.1.0

v2.0.1

Compare Source

  • Disable extension-less imports. If you've used /chacha, switch to /chacha.js now. See 2.0.0 for more details.
  • package.json: specify exported submodules to ensure typescript autocompletion
GitHub Immutable Releases

This GH release does not include NPM & JSR attestations, until we fix bugs related to newly added GitHub Immutable Releases

Full Changelog: paulmillr/noble-ciphers@2.0.0...2.0.1

v2.0.0

Compare Source

High-level
  • The package is now ESM-only. ESM can finally be loaded from common.js on node v20.19+
    • Node v20.19 is now the minimum required version
    • Package imports now work correctly in bundler-less environments, such as browsers
    • Reduces npm package size (traffic consumed): 118KB => 99KB
    • Reduces unpacked npm size (on-disk space): 753KB => 458KB
  • Make bundle sizes smaller, compared to v1.x
  • .js extension must be used for all modules
    • Old: @noble/ciphers/aes
    • New: @noble/ciphers/aes.js
    • This simplifies working in browsers natively without transpilers
Changes
  • webcrypto: move randomBytes and managedNonce to utils.js
  • ghash, poly1305, polyval: only allow Uint8Array as hash inputs, prohibit string
  • utils: new abytes; remove ahash, toBytes
  • Remove modules _assert (use utils), _micro and crypto (use webcrypto)
  • Upgrade typescript compilation env to ts5.9 and es2022
  • Massively improve error messages, make them more descriptive

Full Changelog: paulmillr/noble-ciphers@1.3.0...2.0.0


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the maintenance label Aug 25, 2025
@renovate

renovate Bot commented Aug 25, 2025

Copy link
Copy Markdown
Contributor Author

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@renovate
renovate Bot force-pushed the renovate/noble-ciphers-2.x branch 2 times, most recently from de43113 to 9cca339 Compare August 25, 2025 22:30
@renovate
renovate Bot force-pushed the renovate/noble-ciphers-2.x branch 2 times, most recently from 3911755 to 7d80faf Compare September 8, 2025 05:11
@renovate
renovate Bot force-pushed the renovate/noble-ciphers-2.x branch 2 times, most recently from 0046968 to c61568e Compare September 22, 2025 05:13
@renovate
renovate Bot force-pushed the renovate/noble-ciphers-2.x branch from c61568e to 9bc16c0 Compare September 22, 2025 17:06
@renovate
renovate Bot force-pushed the renovate/noble-ciphers-2.x branch from 9bc16c0 to 649b847 Compare October 6, 2025 04:38
@renovate
renovate Bot force-pushed the renovate/noble-ciphers-2.x branch 2 times, most recently from e23335c to 9d0f5dc Compare October 14, 2025 08:53
@renovate
renovate Bot force-pushed the renovate/noble-ciphers-2.x branch 2 times, most recently from 61b39be to 3c5ff99 Compare October 27, 2025 05:25
@renovate
renovate Bot force-pushed the renovate/noble-ciphers-2.x branch 2 times, most recently from 14fed96 to 50e99dd Compare November 3, 2025 06:55
@renovate
renovate Bot force-pushed the renovate/noble-ciphers-2.x branch 2 times, most recently from 1370bc5 to ad95bc1 Compare November 20, 2025 21:31
@renovate
renovate Bot force-pushed the renovate/noble-ciphers-2.x branch from ad95bc1 to cdc4158 Compare November 24, 2025 04:51
@renovate
renovate Bot force-pushed the renovate/noble-ciphers-2.x branch 2 times, most recently from 82a0efb to 5d4ea68 Compare December 7, 2025 05:15
@renovate
renovate Bot force-pushed the renovate/noble-ciphers-2.x branch from 5d4ea68 to 13db59c Compare April 11, 2026 22:01
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