v6.0.5

Pull in an even more fault-tolerant version of gocomposeapi

v6.0.4

Add retry logic to the most error prone Compose API call

v6.0.3

Pull in a new version of gocomposeapi

It should be slightly more robust

v6.0.2

• Do not attempt to scale a deployment when editing the comments

v6.0.1

• The latest gocomposeapi code is significantly less likely to throw panics due to memory violations.

v6.0.0

• If an existing deployment is far larger than the specified scaling, warn the user and do not attempt to rescale the deployment.

This is a breaking change to Pachelbel's behavior.

v5.3.0

Build the release image from scratch to make it smaller.

v5.2.0

Users cannot downscale a deployment below its current usage

The API call itself would fail if a user did this, but the
error is opaque. Instead we can fail while building actions
with a much cleaner error message

v5.1.0

Add 'address_translations' as an optional field of the output schema

This is a required addition to properly support scylladb (https://help.compose.com/docs/scylla-address-translation-maps)

v5.0.0

Breaking API Change:

• Pachelbel no longer performs in-place upgrades by default. See updates to the v1_schema for more details.