Update dependency earthly/earthly to v0.8.9

renovate[bot] · web-flow · commit bbf7f51bcf94 · 2024-04-24T18:32:55.000Z
diff --git a/docs/basics/part-8a-using-earthly-in-your-current-ci.md b/docs/basics/part-8a-using-earthly-in-your-current-ci.md
@@ -41,7 +41,7 @@ jobs:
     steps:
     - uses: earthly/actions/setup-earthly@v1
       with:
-        version: v0.8.6
+        version: v0.8.9
     - uses: actions/checkout@v2
     - name: Docker Login
       run: docker login --username "$DOCKERHUB_USERNAME" --password "$DOCKERHUB_TOKEN"
@@ -51,7 +51,7 @@ jobs:
 
 Here is an explanation of the steps above:
 
-* The action `earthly/actions/setup-earthly@v1` downloads and installs Earthly. Running this action is similar to running the Earthly installation one-liner `sudo /bin/sh -c 'wget https://github.com/earthly/earthly/releases/download/v0.8.6/earthly-linux-amd64 -O /usr/local/bin/earthly && chmod +x /usr/local/bin/earthly'`
+* The action `earthly/actions/setup-earthly@v1` downloads and installs Earthly. Running this action is similar to running the Earthly installation one-liner `sudo /bin/sh -c 'wget https://github.com/earthly/earthly/releases/download/v0.8.9/earthly-linux-amd64 -O /usr/local/bin/earthly && chmod +x /usr/local/bin/earthly'`
 * The command `docker login` performs a login to the DockerHub registry. This is required, to prevent rate-limiting issues when using popular base images.
 * The command `earthly --org ... --sat ... --ci --push +build` executes the build. The `--ci` flag is used here, in order to force the use of `--strict` mode. In `--strict` mode, Earthly prevents the use of features that make the build less repeatable and also disables local outputs -- because artifacts and images resulting from the build are not needed within the CI environment. Any outputs should be pushed via `RUN --push` or `SAVE IMAGE --push` commands. The flags `--org` and `--sat` allow you to select the organization and satellite to use for the build. If no satellite is specified, the build will be executed in the CI environment itself, with limited caching.
 
diff --git a/docs/ci-integration/build-an-earthly-ci-image.md b/docs/ci-integration/build-an-earthly-ci-image.md
@@ -18,7 +18,7 @@ This guide will cover both approaches to constructing your image.
 This is the recommended approach when adopting Earthly into your containerized CI. Start by basing your custom image on ours:
 
 ```docker
-FROM earthly/earthly:v0.8.6
+FROM earthly/earthly:v0.8.9
 RUN ... # Add your agent, certificates, tools...
 ```
 
@@ -50,7 +50,7 @@ In this setup, Earthly will be allowed to manage an instance of its `earthly/bui
 To enable this, simply follow the installation instructions within your Dockerfile/Earthfile as you would on any other host. An example of installing this can be found below.
 
 ```docker
-RUN wget https://github.com/earthly/earthly/releases/download/v0.8.6/earthly-linux-amd64 -O /usr/local/bin/earthly && \
+RUN wget https://github.com/earthly/earthly/releases/download/v0.8.9/earthly-linux-amd64 -O /usr/local/bin/earthly && \
     chmod +x /usr/local/bin/earthly && \
     /usr/local/bin/earthly bootstrap
 ```
diff --git a/docs/ci-integration/guides/bitbucket-pipelines-integration.md b/docs/ci-integration/guides/bitbucket-pipelines-integration.md
@@ -7,7 +7,7 @@ You can however, run Earthly builds on Bitbucket pipelines via [remote runners](
 ```yml
 # ./bitbucket-pipelines.yml
 
-image: earthly/earthly:v0.8.6
+image: earthly/earthly:v0.8.9
 
 pipelines:
   default:
diff --git a/docs/ci-integration/guides/circle-integration.md b/docs/ci-integration/guides/circle-integration.md
@@ -14,7 +14,7 @@ jobs:
     steps:
       - checkout
       - run: docker login --username "$DOCKERHUB_USERNAME" --password "$DOCKERHUB_TOKEN"
-      - run: "sudo /bin/sh -c 'wget https://github.com/earthly/earthly/releases/download/v0.8.6/earthly-linux-amd64 -O /usr/local/bin/earthly && chmod +x /usr/local/bin/earthly'"
+      - run: "sudo /bin/sh -c 'wget https://github.com/earthly/earthly/releases/download/v0.8.9/earthly-linux-amd64 -O /usr/local/bin/earthly && chmod +x /usr/local/bin/earthly'"
       - run: earthly --ci --push +build
 ```
 
diff --git a/docs/ci-integration/guides/codebuild-integration.md b/docs/ci-integration/guides/codebuild-integration.md
@@ -18,7 +18,7 @@ version: 0.2
 phases:
   install:
     commands:
-      - wget https://github.com/earthly/earthly/releases/download/v0.8.6/earthly-linux-amd64 -O /usr/local/bin/earthly && chmod +x /usr/local/bin/earthly
+      - wget https://github.com/earthly/earthly/releases/download/v0.8.9/earthly-linux-amd64 -O /usr/local/bin/earthly && chmod +x /usr/local/bin/earthly
   pre_build:
     commands:
       - echo Logging into Docker
diff --git a/docs/ci-integration/guides/gh-actions-integration.md b/docs/ci-integration/guides/gh-actions-integration.md
@@ -60,7 +60,7 @@ jobs:
     - name: Docker Login
       run: docker login --username "$DOCKERHUB_USERNAME" --password "$DOCKERHUB_TOKEN"
     - name: Download latest earthly
-      run: "sudo /bin/sh -c 'wget https://github.com/earthly/earthly/releases/download/v0.8.6/earthly-linux-amd64 -O /usr/local/bin/earthly && chmod +x /usr/local/bin/earthly'"
+      run: "sudo /bin/sh -c 'wget https://github.com/earthly/earthly/releases/download/v0.8.9/earthly-linux-amd64 -O /usr/local/bin/earthly && chmod +x /usr/local/bin/earthly'"
     - name: Run build
       run: earthly --ci --push +build
 ```
diff --git a/docs/ci-integration/guides/gitlab-integration.md b/docs/ci-integration/guides/gitlab-integration.md
@@ -15,7 +15,7 @@ variables:
   FORCE_COLOR: 1
   EARTHLY_EXEC_CMD: "/bin/sh"
 
-image: earthly/earthly:v0.8.6
+image: earthly/earthly:v0.8.9
 
 before_script:
     - docker login -u $CI_REGISTRY_USER -p $CI_REGISTRY_PASSWORD $CI_REGISTRY
diff --git a/docs/ci-integration/guides/google-cloud-build.md b/docs/ci-integration/guides/google-cloud-build.md
@@ -106,7 +106,7 @@ Running this build will use the [`cloudbuild.yaml`](https://github.com/earthly/c
 
 ```yaml
   - id: 'build'
-    name: 'earthly/earthly:v0.8.6'
+    name: 'earthly/earthly:v0.8.9'
     args:
       - --ci
       - --push
@@ -117,7 +117,7 @@ Running this build will use the [`cloudbuild.yaml`](https://github.com/earthly/c
 
 ```yaml
   - id: 'gcp-test'
-    name: 'earthly/earthly:v0.8.6'
+    name: 'earthly/earthly:v0.8.9'
     args:
       - +gcp-cloudbuild
     secretEnv:
diff --git a/docs/ci-integration/guides/woodpecker-integration.md b/docs/ci-integration/guides/woodpecker-integration.md
@@ -14,7 +14,7 @@ The project needs to be [trusted](https://woodpecker-ci.org/docs/usage/project-s
 #.woodpecker.yml
 pipeline:
   earthly:
-    image: earthly/earthly:v0.8.5
+    image: earthly/earthly:v0.8.9
     volumes:
       - /var/run/docker.sock:/var/run/docker.sock
     environment:
diff --git a/docs/ci-integration/overview.md b/docs/ci-integration/overview.md
@@ -27,7 +27,7 @@ Once you have ensured that the dependencies are available, you'll need to instal
 This is the simplest method for adding `earthly` to your CI. It will work best on dedicated computers, or in scripted/auto-provisioned build environments. You can pin it to a specific version like so:
 
 ```shell
-wget https://github.com/earthly/earthly/releases/download/v0.8.6/earthly-linux-amd64 -O /usr/local/bin/earthly && \
+wget https://github.com/earthly/earthly/releases/download/v0.8.9/earthly-linux-amd64 -O /usr/local/bin/earthly && \
 chmod +x /usr/local/bin/earthly && \
 /usr/local/bin/earthly bootstrap
 ```
diff --git a/docs/ci-integration/use-earthly-ci-image.md b/docs/ci-integration/use-earthly-ci-image.md
@@ -36,19 +36,19 @@ For more details on using remote execution, [see our guide on remote Buildkit](.
 The image expects the source code of the application you are building in the current working directory (by default `/workspace`). You will need to copy or mount the necessary files to that directory prior to invoking the entrypoint.
 
 ```bash
-docker run --privileged --rm -v "$PWD":/workspace earthly/earthly:v0.8.6 +my-target
+docker run --privileged --rm -v "$PWD":/workspace earthly/earthly:v0.8.9 +my-target
 ```
 
 Or, if you would like to use an alternative directory:
 
 ```bash
-docker run --privileged --rm -v "$PWD":/my-dir -w /my-dir earthly/earthly:v0.8.6 +my-target
+docker run --privileged --rm -v "$PWD":/my-dir -w /my-dir earthly/earthly:v0.8.9 +my-target
 ```
 
 Alternatively, you may rely on Earthly to perform a git clone, by using the remote target reference format. For example:
 
 ```bash
-docker run --privileged --rm earthly/earthly:v0.8.6 github.com/foo/bar:my-branch+target
+docker run --privileged --rm earthly/earthly:v0.8.9 github.com/foo/bar:my-branch+target
 ```
 
 #### `NO_BUILDKIT` Environment Variable
diff --git a/docs/cloud/satellites/self-hosted.md b/docs/cloud/satellites/self-hosted.md
@@ -26,7 +26,7 @@ docker run --privileged \
     -e EARTHLY_ORG=my-org \
     -e SATELLITE_NAME=my-satellite \
     -e SATELLITE_HOST=153.65.8.0 \
-  earthly/satellite:v0.8.6
+  earthly/satellite:v0.8.9
 ```
 
 The following environment variables are required:
@@ -107,7 +107,7 @@ runcmd:
         -e EARTHLY_TOKEN=GuFna*****nve7e \
         -e EARTHLY_ORG=my-org \
         -e SATELLITE_NAME=my-satellite \
-        earthly/satellite:v0.8.6
+        earthly/satellite:v0.8.9
 ```
 
 Note that the `SATELLITE_HOST` variable is unset in this example so that the host is auto-discovered by the satellite when it starts. This should result in the instance’s private DNS being used as the host.
@@ -134,7 +134,7 @@ spec:
    valueFrom:
      fieldRef:
        fieldPath: metadata.name
-      image: earthly/satellite:v0.8.6
+      image: earthly/satellite:v0.8.9
       securityContext:
         privileged: true
       ports:
@@ -174,7 +174,7 @@ Here’s an example of how to attach the volume using the Docker command line:
 ```
 docker run -v earthly-cache:/tmp/earthly:rw \
   ...
-  earthly/satellite:v0.8.6
+  earthly/satellite:v0.8.9
 ```
 
 ## Additional Environment Variables
diff --git a/docs/docker-images/all-in-one.md b/docs/docker-images/all-in-one.md
@@ -2,7 +2,7 @@ This image contains `earthly`, `buildkit`, and some extra configuration to enabl
 
 ## Tags
 
-Currently, the `latest` tag is `v0.8.6`.  
+Currently, the `latest` tag is `v0.8.9`.  
 For other available tags, please check out https://hub.docker.com/r/earthly/earthly/tags
 
 ## Quickstart
@@ -14,7 +14,7 @@ Want to get started? Here are a couple sample `docker run` commands that cover t
 This example shows how to use the Earthly container in conjunction with a Docker socket that Earthly can use to start up the Buildkit daemon.
 
 ```bash
-docker run -t -v $(pwd):/workspace -v /var/run/docker.sock:/var/run/docker.sock -e NO_BUILDKIT=1 earthly/earthly:v0.8.6 +for-linux
+docker run -t -v $(pwd):/workspace -v /var/run/docker.sock:/var/run/docker.sock -e NO_BUILDKIT=1 earthly/earthly:v0.8.9 +for-linux
 ```
 
 Here's a quick breakdown:
@@ -30,7 +30,7 @@ Here's a quick breakdown:
 This example shows how the Earthly image can start a Buildkit daemon within the same container. A Docker socket is not needed in this case, however the container will need to be run with the `--privileged` flag.
 
 ```bash
-docker run --privileged -t -v $(pwd):/workspace -v earthly-tmp:/tmp/earthly:rw earthly/earthly:v0.8.6 +for-linux
+docker run --privileged -t -v $(pwd):/workspace -v earthly-tmp:/tmp/earthly:rw earthly/earthly:v0.8.9 +for-linux
 ```
 
 Here's a quick breakdown:
@@ -46,7 +46,7 @@ Here's a quick breakdown:
 This example utilizes an [Earthly Satellite](https://docs.earthly.dev/earthly-cloud/satellites) to perform builds. The code to be built is downloaded directly from GitHub.
 
 ```bash
-docker run -t -e NO_BUILDKIT=1 -e EARTHLY_TOKEN=<my-token> earthly/earthly:v0.8.6 --ci --org <my-org> --sat <my-sat> github.com/earthly/earthly+for-linux
+docker run -t -e NO_BUILDKIT=1 -e EARTHLY_TOKEN=<my-token> earthly/earthly:v0.8.9 --ci --org <my-org> --sat <my-sat> github.com/earthly/earthly+for-linux
 ```
 
 Here's what this does:
@@ -61,11 +61,11 @@ Here's what this does:
 This example shows how to use the Earthly container to run non-build commands. This is useful for running commands like `earthly account`, or `earthly secret`.
 
 ```bash
-docker run -t -e NO_BUILDKIT=1 -e EARTHLY_TOKEN=<my-token> earthly/earthly:v0.8.6 account list-tokens
+docker run -t -e NO_BUILDKIT=1 -e EARTHLY_TOKEN=<my-token> earthly/earthly:v0.8.9 account list-tokens
 ```
 
 ```bash
-docker run -t -e NO_BUILDKIT=1 -e EARTHLY_TOKEN=<my-token> earthly/earthly:v0.8.6 secret get foo
+docker run -t -e NO_BUILDKIT=1 -e EARTHLY_TOKEN=<my-token> earthly/earthly:v0.8.9 secret get foo
 ```
 
 ## Using This Image
diff --git a/docs/docker-images/buildkit-standalone.md b/docs/docker-images/buildkit-standalone.md
@@ -4,7 +4,7 @@ This image contains `buildkit` with some Earthly-specific setup. This is what Ea
 
 ## Tags
 
-Currently, the `latest` tag is `v0.8.6`.  
+Currently, the `latest` tag is `v0.8.9`.  
 For other available tags, please check out https://hub.docker.com/r/earthly/buildkitd/tags
 
 ## Quickstart
diff --git a/docs/guides/importing.md b/docs/guides/importing.md
@@ -96,7 +96,7 @@ Here are some examples:
 
 * `+build`
 * `./js+deps`
-* `github.com/earthly/earthly:v0.8.6+earthly`
+* `github.com/earthly/earthly:v0.8.9+earthly`
 * `my-import+build`
 
 ## Artifact reference
@@ -110,7 +110,7 @@ Here are some examples:
 * `+build/my-artifact`
 * `+build/some/artifact/deep/in/a/dir`
 * `./js+build/dist`
-* `github.com/earthly/earthly:v0.8.6+earthly/earthly`
+* `github.com/earthly/earthly:v0.8.9+earthly/earthly`
 * `my-import+build/my-artifact`
 
 ## Image reference
@@ -131,7 +131,7 @@ Here are some examples:
 
 * `+COMPILE`
 * `./js+NPM_INSTALL`
-* `github.com/earthly/earthly:v0.8.6+DOWNLOAD_DIND`
+* `github.com/earthly/earthly:v0.8.9+DOWNLOAD_DIND`
 * `my-import+COMPILE`
 
 For more information on functions, see the [Functions Guide](./functions.md).
@@ -170,7 +170,7 @@ Another form of a Earthfile reference is the remote form. In this form, the reci
 |----|----|----|----|
 | `<vendor>/<namespace>/<project>/path/in/project[:some-tag]` | `<vendor>/<namespace>/<project>/path/in/project[:some-tag]+<target-name>` | `<vendor>/<namespace>/<project>/path/in/project[:some-tag]+<target-name>/<artifact-path>` | `<vendor>/<namespace>/<project>/path/in/project[:some-tag]+<function-name>` |
 | `github.com/earthly/earthly/buildkitd` | `github.com/earthly/earthly/buildkitd+build` | `github.com/earthly/earthly/buildkitd+build/out.bin` | `github.com/earthly/earthly/buildkitd+COMPILE` |
-| `github.com/earthly/earthly:v0.8.6` | `github.com/earthly/earthly:v0.8.6+build` | `github.com/earthly/earthly:v0.8.6+build/out.bin` | `github.com/earthly/earthly:v0.8.6+COMPILE` |
+| `github.com/earthly/earthly:v0.8.9` | `github.com/earthly/earthly:v0.8.9+build` | `github.com/earthly/earthly:v0.8.9+build/out.bin` | `github.com/earthly/earthly:v0.8.9+COMPILE` |
 
 ### Import reference
 
@@ -180,7 +180,7 @@ Finally, the last form of Earthfile referencing is an import reference. Import r
 |----|----|----|----|----|
 | `IMPORT <full-earthfile-ref> AS <import-alias>` | `<import-alias>` | `<import-alias>+<target-name>` | `<import-alias>+<target-name>/<artifact-path>` | `<import-alias>+<function-name>` |
 | `IMPORT github.com/earthly/earthly/buildkitd` | `buildkitd` | `buildkitd+build` | `buildkitd+build/out.bin` | `buildkitd+COMPILE` |
-| `IMPORT github.com/earthly/earthly:v0.8.6` | `earthly` | `earthly+build` | `earthly+build/out.bin` | `earthly+COMPILE` |
+| `IMPORT github.com/earthly/earthly:v0.8.9` | `earthly` | `earthly+build` | `earthly+build/out.bin` | `earthly+COMPILE` |
 
 Here is an example in an Earthfile:
 
diff --git a/docs/guides/target-ref.md b/docs/guides/target-ref.md
@@ -20,7 +20,7 @@ Here are some examples:
 
 * `+build`
 * `./js+deps`
-* `github.com/earthly/earthly:v0.8.6+earthly`
+* `github.com/earthly/earthly:v0.8.9+earthly`
 
 ## Artifact reference
 
@@ -33,7 +33,7 @@ Here are some examples:
 * `+build/my-artifact`
 * `+build/some/artifact/deep/in/a/dir`
 * `./js+build/dist`
-* `github.com/earthly/earthly:v0.8.6+earthly/earthly`
+* `github.com/earthly/earthly:v0.8.9+earthly/earthly`
 
 ## Image reference
 
@@ -53,7 +53,7 @@ Here are some examples:
 
 * `+COMPILE`
 * `./js+NPM_INSTALL`
-* `github.com/earthly/earthly:v0.8.6+DOWNLOAD_DIND`
+* `github.com/earthly/earthly:v0.8.9+DOWNLOAD_DIND`
 
 For more information on functions, see the [functions guide](./functions.md).
 
@@ -93,7 +93,7 @@ Another form of a project reference is the remote form. In this form, the recipe
 |----|----|----|----|
 | `<vendor>/<namespace>/<project>/path/in/project[:some-tag]` | `<vendor>/<namespace>/<project>/path/in/project[:some-tag]+<target-name>` | `<vendor>/<namespace>/<project>/path/in/project[:some-tag]+<target-name>/<artifact-path>` | `<vendor>/<namespace>/<project>/path/in/project[:some-tag]+<function-name>` |
 | `github.com/earthly/earthly/buildkitd` | `github.com/earthly/earthly/buildkitd+build` | `github.com/earthly/earthly/buildkitd+build/out.bin` | `github.com/earthly/earthly/buildkitd+COMPILE` |
-| `github.com/earthly/earthly:v0.8.6` | `github.com/earthly/earthly:v0.8.6+build` | `github.com/earthly/earthly:v0.8.6+build/out.bin` | `github.com/earthly/earthly:v0.8.6+COMPILE` |
+| `github.com/earthly/earthly:v0.8.9` | `github.com/earthly/earthly:v0.8.9+build` | `github.com/earthly/earthly:v0.8.9+build/out.bin` | `github.com/earthly/earthly:v0.8.9+COMPILE` |
 
 ### Import reference
 
@@ -103,7 +103,7 @@ Finally, the last form of project referencing is an import reference. Import ref
 |----|----|----|----|----|
 | `IMPORT <full-project-ref> AS <import-alias>` | `<import-alias>` | `<import-alias>+<target-name>` | `<import-alias>+<target-name>/<artifact-path>` | `<import-alias>+<function-name>` |
 | `IMPORT github.com/earthly/earthly/buildkitd` | `buildkitd` | `buildkitd+build` | `buildkitd+build/out.bin` | `buildkitd+COMPILE` |
-| `IMPORT github.com/earthly/earthly:v0.8.6` | `earthly` | `earthly+build` | `earthly+build/out.bin` | `earthly+COMPILE` |
+| `IMPORT github.com/earthly/earthly:v0.8.9` | `earthly` | `earthly+build` | `earthly+build/out.bin` | `earthly+COMPILE` |
 
 Here is an example in an Earthfile:
 
diff --git a/release/README.md b/release/README.md
@@ -18,7 +18,7 @@
   git checkout main && git pull
   ```
 * Update the CHANGELOG.md with the corresponding release notes and open a PR
-  * Use a comparison such as https://github.com/earthly/earthly/compare/v0.8.6...main (replace the versions in the URL with the previously released version) or a tool such as `gitk` (aka `git-gui`) to see which PRs will go into this release.
+  * Use a comparison such as https://github.com/earthly/earthly/compare/v0.8.9...main (replace the versions in the URL with the previously released version) or a tool such as `gitk` (aka `git-gui`) to see which PRs will go into this release.
 * Make sure that main build is green for all platforms (check build status for the latest commit on GitHub).
 * Make sure the following build status are green:
   | Platform      | Status        |
