5.2.0 - Flow 7 compatibility

What's Changed

• Flow 7 compatibility by @kdambekalns in #22

Full Changelog: 5.1.2...5.2.0

5.1.2: Set Cache-Control for object in one-bucket setups

This fixes a bug where the Cache-Control header was not set when an
object was published in a setup where storage and target buckets are
the same.

Resolves #20

Bugfix release for URI encoding

BUGFIX: Make sure public URI gets escaped

Employ guzzle PSR-7 Uri to make sure the generated
public URIs are properly escaped.

Flow 6.0 Compatibility and Signed Resource URIs

This release comes with a few changes which makes the package compatible with Flow 6.0 and Neos 5.0. Note that the minimum requirement was also raised to Flow 5.2 and Neos 4.2 respectively.

Besides the clean up and adjustments, this version also introduces two new features: customizable patterns for the persistent resources URIs and support for URIs giving access to protected resources for a limited time (aka "secure downloads"). See the updated README for more details.

4.5.1

Throw exception on start if bucket name is missing

4.5.0

Introduce --startSha1 option

4.4.4

Remove entity manager inject in GCSCommandController

4.4.3

Fix updateResourceMetadataCommand for Flow 4.x

4.4.2

Optimize memory usage for updateResourceMetadata

4.4.1: Retry and exponential backoff for publishing to same bucket

This change adds code which should protect against rate limit problems
which may occurr when updating the same Google Cloud Storage object
multiple times during one second.

The code is speculative because it could not be reproduced locally yet.