v3.12.1

 - [readme] minor cleanups
 - [meta] document support as node 0.10+
 - [meta] add `sideEffects` flag
 - [meta] update repo URLs
 - [Deps] pin `hash-base` to ~3.0, due to a breaking change
 - [Deps] update `browserify-cipher`, `browserify-sign `, `create-ecdh`, `create-hash`, `create-hmac`, `diffie-hellman`, `inherits`, `pbkdf2`, `public-encrypt`, `randombytes`, `randomfill`
 - [Dev Deps] update `@ljharb/eslint-config`, `object.entries`, `safe-buffer`, `tape`
 - [Tests] ignore the "low" warning from elliptic
 - [Tests] node 22+ removes `crypto.createCipher`
 - [Tests] add `nyc`
 - [Tests] replace `aud` with `npm audit`
 - [Tests] remove zuul; it’s dead
 - [Tests] skip `engines` check for now
 - [Tests] mostly switch to Github Actions
 - [Tests] node 17 doesn’t support rmd160
 - [Tests] node 17+ requires a DH key length of >= 512
 - [Tests] rename test scripts to match my conventions
 - [Tests] refactor so tests are not recursive
 - [eslint] switch to eslint
 - Only apps should have lockfiles
 - fix debian issue (maybe)
 - standard fix

Author: ljharb

package.json

@@ -2,7 +2,7 @@
 	"author": "Dominic Tarr <[email protected]> (dominictarr.com)",
 	"name": "crypto-browserify",
 	"description": "implementation of crypto for the browser",
-	"version": "3.12.0",
+	"version": "3.12.1",
 	"homepage": "https://github.com/browserify/crypto-browserify",
 	"sideEffects": false,
 	"repository": {