chore(CFN): Adding cfn template (#780)

fix: Add packaging dependency for twine < 4.0 (#522)

* chore: Adds pyhton36 deprecation to changelog

* fix: updates compatability test to 3.7

* fix: pin tox dependency < 4.0

* fix: reword the deprecation announcement

* chore: Update SUPPORT_POLICY.rst

* fix: Add Maintenance Date in SUPPORT_POLICY.rst

Co-authored-by: Tony Knapp <5892063+texastony@users.noreply.github.com>

* fix: SUPPORT_POLICY.rst

Co-authored-by: Tony Knapp <5892063+texastony@users.noreply.github.com>

* fix: Add packaging dependency for twine

Co-authored-by: Shubham Chaturvedi <scchatur@amazon.com>
Co-authored-by: Shubham Chaturvedi <shubhamchaturvedi7@gmail.com>
Co-authored-by: Tony Knapp <5892063+texastony@users.noreply.github.com>

chore: Mark 2.x as End-of-Support (#481)

* chore: Mark 2.x as End-of-Support

* fix: tox dependency

Co-authored-by: Shubham Chaturvedi <scchatur@amazon.com>

chore: Mark 1.x as End-of-Support (#480)

* chore: Mark 1.x as End-of-Support

* fix: pin tox and flake8 dependencies

Co-authored-by: Shubham Chaturvedi <scchatur@amazon.com>

chore: CHANGELOG and version bump for release 3.1.0 (#189)

chore: Remove support for python 2 (#173)

chore: Prep for release 2.1.0 (#172)

fix!: Remove the MostRecentProvider.

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

feat: Adds the CachingMostRecentProvider. Deprecates MostRecentProvider.

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.

Bump to v1.2.0 (#130)


* bump to 1.2.0 and update changelog with possible breaking change note