6.0.0-alpha1

What's Changed

• MNT Run module-standardiser by @emteknetnz in #55
• MNT Run module-standardiser by @GuySartorelli in #57
• MNT Run module-standardiser by @GuySartorelli in #59
• DEP Dependencies for CMS 6 by @emteknetnz in #60
• MNT Run module-standardiser by @emteknetnz in #62
• MNT Run module-standardiser by @emteknetnz in #63
• MNT Run module-standardiser by @GuySartorelli in #67
• MNT Run module-standardiser by @GuySartorelli in #68
• DEP Use PHPUnit 11 by @emteknetnz in #69

Full Changelog: 5.0.1...6.0.0-alpha1

5.0.1

What's Changed

• DEP Update minimum version of aws/aws-sdk-php by @emteknetnz in #53

Full Changelog: 5.0.0...5.0.1

5.0.0

What's Changed

• CMS 5 compatability by @GuySartorelli in #46
• MNT Test dynamodb integration works by @emteknetnz in #49

New Contributors

• @GuySartorelli made their first contribution in #46
• @emteknetnz made their first contribution in #49

Full Changelog: 4.1.0...5.0.0

5.0.0-rc1

What's Changed

• CMS 5 compatability by @GuySartorelli in #46
• MNT Test dynamodb integration works by @emteknetnz in #49

New Contributors

• @GuySartorelli made their first contribution in #46
• @emteknetnz made their first contribution in #49

Full Changelog: 4.1.0...5.0.0-rc1

5.0.0-beta1

What's Changed

• CMS 5 compatability by @GuySartorelli in #46

New Contributors

• @GuySartorelli made their first contribution in #46

Full Changelog: 4.1.0...5.0.0-beta1

4.1.0

What's Changed

• Binary safe session (using SDK fix) by @dnsl48 in #38
• Local development README by @chillu in #34
• DOCS Clarify GC handling, remove crontask dep (fixes #39) by @chillu in #40

Full Changelog: 4.0.2...4.1.0

4.0.2

Fixed a regression caused by silverstripe/[email protected], which introduced safeguards around web-based administrative tasks triggered through URL paths and parameters. See CVE-2019-12246: Denial of Service on flush and development URL tools.

When using this framework release, and triggering administrative actions such as ?flush=1, dev/build, or dev/tasks/*, the confirmation token required for CSRF protection could not be set in the session. This prevented the task from passing the new confirmation step. The regression occurred when the silverstripe/dynamodb module is installed, and is activated through environment constants (which is the default configuration in SilverStripe Platform for stacks with multiple server environments).

The fix (#32) can be applied to existing SilverStripe environments with existing session data managed through the module. It should not cause users from losing session data, or being logged out of the CMS. On the next write to existing sessions, existing session data will automatically be converted to a binary-safe persistence format. New sessions will write in the correct format by default.

4.0.1

Use new Environment API in SilverStripe 4 to get environment constants, see #30

Remove the session GC task and API

Since 2017-02 dynamodb now can automatically and freely run garbage collection on tables. It's more cost effective and have no performance impact on sites using dynamodb as a session storage.

source: https://aws.amazon.com/about-aws/whats-new/2017/02/amazon-dynamodb-now-supports-automatic-item-expiration-with-time-to-live-ttl/

Update your project with composer require "silverstripe/dynamodb": "^3.0"

This is a backport of 5983c48 but for SilverStripe 3

Use latest patch release of AWS SDK

Merge pull request #19 from silverstripe/use-latest-point-release

Ensure we use latest 3.18.x point release for AWS PHP SDK.