Skip to content

v0.7.1

Choose a tag to compare

@rdimitrov rdimitrov released this 19 Nov 13:44
Immutable release. Only release title and notes can be modified.

Final release of the legacy go-tuf module

This is the last release of github.com/theupdateframework/go-tuf (v0.x). The module is deprecated in favour of go-tuf/v2 (github.com/theupdateframework/go-tuf/v2).

The legacy module receives no further updates, including security fixes. Please migrate to go-tuf/v2.

What changed since v0.7.0

There are no functional changes.

  • The module and all of its public packages are marked as deprecated, so go get, go list -m -u, pkg.go.dev, gopls and staticcheck now report it (#809, closes #655).
  • A test that failed at random on Go 1.24 and later is fixed (#808, closes #728).
  • Dependency updates that were already on the v0.7.0 branch (#579):
    • golang.org/x/crypto v0.16.0 to v0.18.0
    • golang.org/x/term v0.15.0 to v0.16.0
    • golang.org/x/sys v0.15.0 to v0.16.0
    • github.com/secure-systems-lab/go-securesystemslib v0.7.0 to v0.8.0

What to expect when upgrading

  • Tools that honour Go deprecation notices flag imports of this module. With staticcheck this is SA1019.
  • The minimum Go version is unchanged (Go 1.20).
  • Dependencies were deliberately not refreshed further. Doing so would raise the minimum Go version to 1.26 for every consumer. The versions in go.mod are minimums, so your build already uses the newest version required anywhere in your module graph.
  • No tuf or tuf-client binaries are published for this release.

Migrating

  • client is replaced by github.com/theupdateframework/go-tuf/v2/metadata/updater.
  • data is replaced by github.com/theupdateframework/go-tuf/v2/metadata.
  • The examples show a client, a repository and multi-repository use with go-tuf/v2.

Thanks to @NopeCharon for both changes in this release.