Depot CLI 0.1.0

Breaking Changes

This release changes the default behavior of depot build to leave the built image in the builder instance cache and not transfer the resulting image locally (previously known as the --no-load flag).

There are two main reasons for this change:

• The new behavior matches docker buildx build when using a remote builder instance or when running in CI
• Needing to constantly specify --no-load for local builds to skip the image transfer step was tedious

There are now three different depot build behaviors to choose from:

1. depot build ... — builds and leave the resulting image in the builder instance cache
2. depot build --load ... — builds, downloads, and loads the resulting image into the local Docker daemon
3. depot build --push .. — builds and pushes the resulting image to a remote registry, directly from the builder instance

If you need to docker run an image locally that was just built with depot build, you should specify the --load flag. If you do not need this, then omitting the flag will be faster, as it will skip the unnecessary image download step.

What's Changed

• Make --no-load the default behavior (#33) @jacobwgillespie
• Bump docker/setup-qemu-action from 1 to 2 (#30) @dependabot
• Bump docker/build-push-action from 2 to 3 (#32) @dependabot
• Bump docker/login-action from 1 to 2 (#31) @dependabot
• Bump docker/setup-buildx-action from 1 to 2 (#29) @dependabot
• Bump docker/metadata-action from 3 to 4 (#28) @dependabot
• Remove unused API method handler (#27) @jacobwgillespie