fix(deps): update module github.com/tink-crypto/tink-go/v2 to v2.3.0 #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v2.2.0
->v2.3.0
Release Notes
tink-crypto/tink-go (github.com/tink-crypto/tink-go/v2)
v2.3.0
Compare Source
This is Tink Go 2.3.0
What's new
The complete list of changes since 2.2.0 can be found here.
New APIs
Keyset Handle and Manager
keyset.Handle
:Len()
,Primary()
, andEntry(i int)
.keyset.Manager
makes a deep copy of the keyset on calls toHandle()
.AddKey
andAddNewKeyFromParameters
tokeyset.Manager
Key
andParameters
interface which represent keys and theirparameters. Added
key.Parameters
andkey.Key
definitions for:Ed25519
keyset.Handle
NewHandle.*
APIs accept only valid keysets; expectparsing of invalid proto keysets to fail for invalid keysets. With this
change, tests that create keysets with an empty or invalid
KeyData
andexpect a failure on primitive creation will now fail. The user can still
create an empty
keyset.Handle
, for which all methods fail. A valid keysetis such that:
ENABLED
keyset.ReadWithContext
andkeyset.WriteWithContext
that use thetink.AEADWithContext
interface.WriteWithNoSecrets
fail with anil
proto keyset consistently withall other
Write.*
methods.Other
insecuresecretdataaccess.Token
struct to track and optionallyrestrict raw key material access, and
secretdata.Bytes
to wrap accesscontrolled key bytes. In tests,
insecuresecretkeyaccesstest.Token()
can beused.
tink.AEADWithContext
interface, which allows acontext.Context
to be passed along. KMS implementations should prefer this interface when
implementing a remote AEAD.
changed). Users should not rely on specific encodings produced by Tink.
golang.org/x/crypto
to v0.31.0google.golang.org/protobuf
to v1.36.0golang.org/x/sys
to v0.28.0Removed APIs
import tink-go as a pure Bazel dependency (
bazel_dep
) in theirMODULE.bazel
file. However, Bazel users can continue importing tink-gousing bazel-gazelle. If this
causes any issues in your project, please file an issue.
Key
field. This was added bymistake.
primitiveset.PrimitiveSet
,keyset.Primitives
andkeyset.PrimitivesWithKeyManager
from the public API. This API was neverreally intended to be used outside Tink. We are making changes to Tink
internals and we prefer to break users at compile time. If this affects you,
please file an issue.
Future work
To see what we're working towards, check our project roadmap.
Get started
To get started using Tink, see the setup guide.
Go tooling
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.