Release notes from aws-dynamodb-encryption-java

v1.15.2

2022-01-06T22:24:16Z

ci: backport codebuild release from 2.x (aws#229)

v2.0.3

2021-10-14T18:53:57Z

chore: bump version to 2.0.3, update changelog (aws#160)

v2.0.2

2021-09-01T23:56:56Z

fix: updating version in pom in order to build in test-release (aws#156)

v2.0.1

2021-02-12T00:49:24Z

Fix release date of 2.0.1 in changelog

v1.15.1: Merge pull request #135 from robin-aws/fix-changelog-1.15.1-date

2021-02-12T00:49:24Z

Fix release date on 1.15.1

v2.0.0: fix!: Remove the MostRecentProvider.

2021-02-04T22:13:33Z

BREAKING CHANGE: Removes the MostRecentProvider, which is replaced by the CachingMostRecentProvider.

v1.15.0: feat: Adds the CachingMostRecentProvider. Deprecates MostRecentProvider.

2021-02-04T19:47:23Z

Time-based key re-authorization logic in MostRecentProvider did not re-authorize the use of the key
after key usage permissions were changed at the key provider (for example AWS Key Management
Service). This created the potential for keys to be used in the DynamoDB Encryption Client after
permissions to do so were revoked.

The MostRecentProvider is deprecated. It is removed in 2.0.0. New deployments should use the
CachingMostRecentProvider, and existing deployments should upgrade as soon as possible. See
https://docs.aws.amazon.com/dynamodb-encryption-client/latest/devguide/most-recent-provider.html#mrp-versions
for more details.

This change also addresses interoperability issues between the Python and Java implementations of
the DynamoDB Encryption Client.

1.13.0: Merge pull request #67 from johnwalker/newrelease

2018-12-10T22:33:09Z

Update to correct release date

1.12.0: Merge pull request #51 from SalusaSecondus/issue-32

2018-08-29T22:58:59Z

Force use of SaveBehavior.PUT or SaveBehavior.CLOBBER. Issue aws#32

1.11.2

2018-08-03T21:12:28Z

Bump patch version to 1.11.2