What's new

The concept of config variables has been added. Config variables allow you simplify your configuration file, and document and codify the different options available to a developer using your tasks.
They are useful for a number of use cases:
- Reducing duplication in configuration files
- Simplifying management of developer-specific preferences (eg. a developer's preferred log output level)
- Simplifying management of sets of environment-specific settings (eg. managing sets of test environment connection settings for a CI server)
Config variables can currently be used in environment variables for containers and tasks, and build args for containers.
There is more information on config variables in the documentation.
It is now possible to override the image used by a container on the command line.
./batect --override-image build-env=ruby:2.7.0 unitTest will run the unitTest task with the build-env container using the ruby:2.7.0 container.
An extra section has been added to the CircleCI documentation page, showing how to define a reusable command that runs batect (thanks to @ineffyble for the contribution offline)

What's changed

The output of ./batect --help has been improved to make it more readable: the options are now shown in groups and the descriptions wrap at the edge of your terminal window.
Pre-release versions of batect are no longer uploaded to Bintray due to space constraints. Pre-release versions will be made available again in the future.

A clearer error message will now be shown when attempting to run batect on Windows when Docker is configured for Windows containers. (Running Windows containers with batect is not currently supported.)
The issue where batect may randomly freeze, particularly on Windows, has been fixed.

First time using batect? Take a look at the getting started guide, or the many sample projects.

If you're already using batect, run ./batect --upgrade to upgrade automatically.