v1.6.8
What's Changed
- downgrade the go version to 1.25.0 and add go toolchain by @Nicolas-Peiffer in #139
- fix: restore
eclipse-keypontmodule path; refresh README install command, Go Reference badge and documentation links
Full Changelog: v1.6.5...v1.6.8
Module path restored — github.com/eclipse-keypont/crypto11
This release restores the correct module path following the repository move from
github.com/ThalesGroup/crypto11 to github.com/eclipse-keypont/crypto11.
Migrating
go get github.com/eclipse-keypont/crypto11@v1.6.8-import "github.com/ThalesGroup/crypto11"
+import "github.com/eclipse-keypont/crypto11"The old path is deprecated and frozen at
ThalesGroup/crypto11@v1.6.7.
It will receive no further updates, including security fixes. GitHub still redirects the old
repository URL, but the Go module path must be updated by hand — go get cannot follow it for you.
If you are already on this path: upgrade v1.6.5 → v1.6.8
v1.6.6 and v1.6.7 declare the old module path and exist only to publish the deprecation
notice for github.com/ThalesGroup/crypto11. They are not usable as
github.com/eclipse-keypont/crypto11 and will fail with:
module declares its path as: github.com/ThalesGroup/crypto11
but was required as: github.com/eclipse-keypont/crypto11
v1.6.8 fixes this, so github.com/eclipse-keypont/crypto11@latest resolves correctly again.
Go version policy
go.mod targets go 1.25.0 with toolchain go1.25.8. The go directive is kept conservative
so this library does not raise the minimum Go version for projects that import it, while
maintainers build and test with the latest patch toolchain. See #137 and #139.
The
v1.6.xseries is the current stable line.v2.x.yongithub.com/eclipse-keypont/crypto11/v2is in
development (v2.0.0-rc3), which is why pkg.go.dev reports a higher tagged major version.