Releases: matthewhartstonge/argon2
v1.3.2
v1.3.1
v1.3.0
1.3.0 (2025-04-22)
Calling Hash caused undefined behaviour if the mode was argon2d. To make this libraries assumptions clearer, due to relying on the underlying golang eXtra crypto libraries (golang.org/x/crypto), we now return an explicit error argon2.ErrModeUnsupported if the mode is specifically argon2d.
The upstream x/crypto maintainers do not believe in adding argon2d support.
Features
- return error on attempting to hash
argon2d. (71f8bcb)
Bug Fixes
- lint: migrates if-else blocks to tagged switches (QF1003). (04cdec5)
v1.2.1
v1.2.0
1.2.0 (2025-03-06)
Features
- deps: upgrades to [email protected]. (9c86600)
note: [email protected] introduced a change in how the go directive works, now enforcing Minimal Version Selection (MVS). The best thing to do is upgrade your Go toolchain to n-1 and set the go directive in your go.mod file to go 1.(N-1).0 - notice the requirement for the patch set to 0.
If you are a library maintainer, PLEASE make sure to only set this to 0 and remove the toolchain directive, otherwise you will make downstream users will cry (myself included).
Why? As part of an internal Go proposal, all golang.org/x libraries now only support n-1.
I propose that each time that a new major Go release 1.N.0 is made, the go directive in all golang.org/x repos will be upgraded to go 1.(N-1).0. For example, when Go 1.28.0 is released, golang.org/x modules would have their go directive set to go 1.27.0.
Refer: https://go.googlesource.com/proposal/+/master/design/69095-x-repo-continuous-go.md
v1.1.1
v1.1.0
v1.0.3
1.0.3 (2024-12-12)
Fixes
- fix: bumps golang.org/x/crypto from 0.30.0 to 0.31.0 to resolve CVE-2024-45337
Miscellaneous Chores
- release 1.0.3 (601f492)