v1.2.0

1.2.0 (2025-03-06)

Features

• deps: upgrades to go@1.23.0. (9c86600)

note: go@1.21 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

1.1.1 (2024-12-23)

Bug Fixes

• cmd/argon2: enable ldflags variable configuration. (988c8fe)

v1.1.0

1.1.0 (2024-12-21)

Features

• cmd/argon2: adds argon2 cli. (32a22f9)
• goreleaser: adds configuration for automated builds. (c8385f8)

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)

v1.0.2

1.0.2 (2024-11-10)

Miscellaneous Chores

• release 1.0.2 (64bcf86)
• chore: Bump golang.org/x/crypto from 0.28.0 to 0.29.0 (7d61928)
• chore: Bump golang.org/x/crypto from 0.27.0 to 0.28.0 (dbe7209)

v1.0.1

1.0.1 (2024-09-12)

Fixes

• chore: Bump golang.org/x/crypto from 0.26.0 to 0.27.0 #50

Miscellaneous Chores

• release 1.0.1 (f68ab6f)

v1.0.0

1.0.0 (2023-12-03)

Versioning Strategy

The API is stable and has been running in production for many years now, therefore won't be changing.

This library has a single dependency on golang.org/x/crypto. This means that as the version of Go is updated there, this library will roll up it's version to a new minor.
Any CVEs/security patches that come through via dependabot, without a resulting Go version update, will become a patch release.

For example:

• If a version of /x/crypto now requires go@1.28, argon2 will go from v1.0.0 -> v1.1.0.
• If x/crypto releases a version that resolves CVEs with no requirement to upgrade Go, then argon2 will go from v1.0.0 -> v1.0.1.

⚠ BREAKING CHANGES

• deps: bump golang.org/x/crypto from 0.13.0 to 0.16.0 now requires go@v1.18 as a minimum.

Features

• deps: bump golang.org/x/crypto from 0.13.0 to 0.16.0 (8dbc527)

v0.3.4

0.3.4 (2023-09-06)

Miscellaneous Chores

• deps: updates dependencies (efcbcce)

v0.3.3

0.3.3 (2023-07-04)

Build

• deps: updates to golang.org/x/crypto@v0.10.0. (d9c0208)

Bug Fixes

• .github/dependabot: fixes branch targets in dependabot configuration. (64ab947)

v0.3.2

v0.3.2 - 2022-11-18

Changed

• deps: updates to golang.org/x/crypto@v0.3.0.
• .github: adjusts dependabot to file version updates against development.

Full Changelog: v0.3.1...v0.3.2