What's new

It's now possible to automatically remove caches for a project. Run ./batect --clean to remove all cache volumes or directories for the current project. See #406 for more background on this feature, and to provide feedback.
It's now possible to set a cache type with the BATECT_CACHE_TYPE environment variable, which removes the need to specify --cache-type=... for each invocation.
The documentation now includes sample configuration snippets for Golang, Gradle, Node.js (both NPM and Yarn) and .NET projects, including how to correctly configure a cache for each.

What's changed

batect will no longer default to fancy output mode if the console dimensions cannot be determined, as this could lead to garbled output.

The issue where output could become garbled if stdin was redirected (eg. when running as part of a Git hook) has been fixed.
The issue where stdin was not connected to containers after a prerequisite task had run has been fixed.
In addition to preventing input to these containers, it also prevented containers from obtaining the current cursor position, which led to garbled output in some situations.
A common example was running dotnet test after a prerequisite that built the application - the test summary would appear at the top of the console instead of at the end of the output. This also caused dotnet test to hang for 10 seconds while it tried twice to (unsuccessfully) get the current cursor position.
The issue where image build output could sometimes be garbled or repeated in interpolated output mode (--output=all) 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.