What's new

• Dependencies for tasks (previously specified with start) can now be specified with dependencies. This makes task definitions consistent with container definitions, which use dependencies for the same purpose.

  ⚠️ start is now deprecated and will be removed in a future release.

• Specifying the project name in a configuration file with project_name is now optional. If the project name is not provided, it will be inferred from the configuration file's parent directory.

  For example, if the configuration file is located at /home/alex/projects/my-cool-app/batect.yml and a project name is not provided, 'my-cool-app' will be used.

• batect can now upgrade itself in place when a new version is released. Run ./batect --upgrade to upgrade your project's installation automatically - there's no need to manually download anything from GitHub. (You'll be prompted to use this command when batect detects that a new version has been released.)

Getting started

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

How to upgrade from previous versions

Already using batect? To install this update, simply replace the batect script in your project with the one attached to this release. (Don't forget to make it executable with chmod +x batect if need be.)

Once you've upgraded to version 0.12, you can use ./batect --upgrade to upgrade automatically.