chore(release): bump version to 0.12.71

CHANGELOG.md

@@ -1,4 +1,43 @@
 
+<a name="0.12.71"></a>
+## [0.12.71](https://github.com/garden-io/garden/compare/0.13.29...0.12.71) (2024-05-02)
+
+### Bug Fixes
+
+* escape rsync special characters in filenames on windows ([#4434](https://github.com/garden-io/garden/issues/4434)) ([#4438](https://github.com/garden-io/garden/issues/4438)) ([8247044a6](https://github.com/garden-io/garden/commit/8247044a6))
+* update version hash if a file is renamed ([0c32af3da](https://github.com/garden-io/garden/commit/0c32af3da))
+* detect overlapping `targetPath` in `generateFiles` ([#4958](https://github.com/garden-io/garden/issues/4958)) ([34eb11a57](https://github.com/garden-io/garden/commit/34eb11a57))
+* **core:** more narrow set of config fields to hash for module versions ([a34bc42f7](https://github.com/garden-io/garden/commit/a34bc42f7))
+* **jib:** fix JDK 17 base url ([9461bbd31](https://github.com/garden-io/garden/commit/9461bbd31))
+* **jib:** allow the usage of the JDK 21 ([90e381d3d](https://github.com/garden-io/garden/commit/90e381d3d))
+* **jib:** fix sha256 hashes for `mvnd` binaries ([4e317efa6](https://github.com/garden-io/garden/commit/4e317efa6))
+* **k8s:** update default Kaniko version ([b0badbdbc](https://github.com/garden-io/garden/commit/b0badbdbc))
+* **k8s:** handle intermittent socket hang up errors ([51458c674](https://github.com/garden-io/garden/commit/51458c674))
+* **mavend:** fix Mavend `sha256` hash for `windows-amd64` binary ([f64ec4e8f](https://github.com/garden-io/garden/commit/f64ec4e8f))
+* **pulumi:** remove PULUMI_EXPERIMENTAL flag due to side effects ([#4617](https://github.com/garden-io/garden/issues/4617)) ([e02f9bf2b](https://github.com/garden-io/garden/commit/e02f9bf2b))
+* **pulumi:** fix pulumi stack tag rm error ([59a054036](https://github.com/garden-io/garden/commit/59a054036))
+* **self-update:** fix target release finding machinery ([9aed119c5](https://github.com/garden-io/garden/commit/9aed119c5))
+* **self-update:** fix list of the latest available versions ([8f4df701b](https://github.com/garden-io/garden/commit/8f4df701b))
+* **template:** allow `null` as a valid argument in helper functions ([05d1dacc1](https://github.com/garden-io/garden/commit/05d1dacc1))
+* **template:** allow empty string as a valid arg of `isEmpty` helper ([66458a9e7](https://github.com/garden-io/garden/commit/66458a9e7))
+* **template-strings:** do not apply helper functions on unresolved string ([#4710](https://github.com/garden-io/garden/issues/4710)) ([8d5180090](https://github.com/garden-io/garden/commit/8d5180090))
+* **terraform:** fix `sha256` hashes for some old terraform binaries ([9a9df415d](https://github.com/garden-io/garden/commit/9a9df415d))
+
+### Features
+
+* update helm to `3.12.0` ([64de8054f](https://github.com/garden-io/garden/commit/64de8054f))
+
+### Improvements
+
+* update docker to v24.0.4 ([13db6076f](https://github.com/garden-io/garden/commit/13db6076f))
+* **helm:** update helm to `3.12.2` ([76b4f70e4](https://github.com/garden-io/garden/commit/76b4f70e4))
+* **jib:** update JDK 17 LTS version to `17.0.9+9` ([3f4a9fcd4](https://github.com/garden-io/garden/commit/3f4a9fcd4))
+* **jib:** support JDK 21 LTS version ([e1e175378](https://github.com/garden-io/garden/commit/e1e175378))
+* **jib:** allow concurrent maven builds ([b34c0fe15](https://github.com/garden-io/garden/commit/b34c0fe15))
+* **jib:** support custom `mvnd` binaries ([00588911a](https://github.com/garden-io/garden/commit/00588911a))
+* **jib:** upgrade Maven Daemon version to `0.9.0` ([45f501b6c](https://github.com/garden-io/garden/commit/45f501b6c))
+* **jib:** upgrade Maven version to `3.8.8` ([ade1e43fa](https://github.com/garden-io/garden/commit/ade1e43fa))
+
 <a name="0.12.70"></a>
 ## [0.12.70](https://github.com/garden-io/garden/compare/0.12.69...0.12.70) (2024-04-25)
 

README.md

@@ -8,7 +8,7 @@
   <span>&nbsp;&nbsp;•&nbsp;&nbsp;</span>
   <a href="https://docs.garden.io/v/acorn-0.12/?utm_source=github">Docs</a>
   <span>&nbsp;&nbsp;•&nbsp;&nbsp;</span>
-  <a href="https://github.com/garden-io/garden/tree/0.12.70/examples">Examples</a>
+  <a href="https://github.com/garden-io/garden/tree/0.12.71/examples">Examples</a>
   <span>&nbsp;&nbsp;•&nbsp;&nbsp;</span>
   <a href="https://garden.io/blog/?utm_source=github">Blog</a>
   <span>&nbsp;&nbsp;•&nbsp;&nbsp;</span>

cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@garden-io/cli",
-  "version": "0.12.70",
+  "version": "0.12.71",
   "description": "Cloud native testing platform for testing and developing container applications on Kubernetes",
   "repository": {
     "type": "git",

core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@garden-io/core",
-  "version": "0.12.70",
+  "version": "0.12.71",
   "description": "A full-featured development framework for containers and serverless",
   "repository": {
     "type": "git",

dashboard/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@garden-io/dashboard",
-  "version": "0.12.70",
+  "version": "0.12.71",
   "private": true,
   "devDependencies": {
     "@garden-io/cli": "*",

docs/advanced/using-remote-sources.md

@@ -11,7 +11,7 @@ You can import **two** types of remote repositories with Garden:
 
 > **Remote _module_**: The source code for a single Garden module. In this case, the `garden.yml` config file is stored in the main project repository while the module code itself is in the remote repository.
 
-The code examples below are from our [remote sources example](https://github.com/garden-io/garden/tree/0.12.70/examples/remote-sources).
+The code examples below are from our [remote sources example](https://github.com/garden-io/garden/tree/0.12.71/examples/remote-sources).
 
 ## Importing Remote Repositories
 

docs/basics/quickstart.md

@@ -206,7 +206,7 @@ If you'd like to better understand how a Garden project is configured when using
 through our [first project tutorial](../tutorials/your-first-project/README.md) which walks you through configuring a Garden project step-by-step.
 
 If you like to dive right in and configure your own project for Garden, we recommend using our [example
-projects on GitHub](https://github.com/garden-io/garden/tree/0.12.70/examples) for reference and reading through the different pages
+projects on GitHub](https://github.com/garden-io/garden/tree/0.12.71/examples) for reference and reading through the different pages
 of the [Using Garden section](../using-garden/configuration-overview.md) of our docs.
 
 And if you have any questions or feedback—or just want to say hi 🙂—we encourage you to join our [Discord community](https://discord.gg/FrmhuUjFs6)!

docs/guides/using-garden-in-ci.md

@@ -23,7 +23,7 @@ The guide uses the [Remote Kubernetes plugin](../k8s-plugins/remote-k8s/README.m
 
 ## Project overview
 
-The project is based on our basic [demo-project](https://github.com/garden-io/garden/tree/0.12.70/examples/demo-project) example, but configured for multiple environments. Additionally it contains a CircleCI config file. You'll find the entire source code [here](https://github.com/garden-io/ci-demo-project).
+The project is based on our basic [demo-project](https://github.com/garden-io/garden/tree/0.12.71/examples/demo-project) example, but configured for multiple environments. Additionally it contains a CircleCI config file. You'll find the entire source code [here](https://github.com/garden-io/ci-demo-project).
 
 The CI pipeline is configured so that Garden tests the project and deploys it to a **preview** environment on every pull request. Additionally, it tests the project and deploys it to a separate **staging** environment on every merge to the `main` branch.
 

docs/k8s-plugins/module-types/container.md

@@ -11,7 +11,7 @@ The Kubernetes plugins can deploy `container` modules that define one or more `s
 
 Garden will take the simplified `container` service specification and convert it to the corresponding Kubernetes manifests, i.e. Deployment, Service and (if applicable) Ingress resources.
 
-Here, for example, is the spec for the `frontend` service in our example [demo project](https://github.com/garden-io/garden/tree/0.12.70/examples/demo-project):
+Here, for example, is the spec for the `frontend` service in our example [demo project](https://github.com/garden-io/garden/tree/0.12.71/examples/demo-project):
 
 ```yaml
 kind: Module
@@ -95,5 +95,5 @@ kubectl --namespace <my-app-namespace> create secret generic --from-literal=some
 
 Where `<my-app-namespace>` is your project namespace (which is either set with `namespace` in your provider config, or defaults to your project name). There are notably other, more secure ways to create secrets via `kubectl`. Please refer to the official [Kubernetes Secrets docs](https://kubernetes.io/docs/concepts/configuration/secret/#creating-a-secret-using-kubectl-create-secret) for details.
 
-Also check out the [Kubernetes Secrets example project](https://github.com/garden-io/garden/tree/0.12.70/examples/kubernetes-secrets) for a working example.
+Also check out the [Kubernetes Secrets example project](https://github.com/garden-io/garden/tree/0.12.71/examples/kubernetes-secrets) for a working example.
 

docs/k8s-plugins/module-types/helm.md

@@ -7,13 +7,13 @@ order: 3
 
 The [Helm](https://helm.sh/) package manager is one of the most commonly used tools for managing Kubernetes manifests. Garden supports using your own Helm charts, alongside your container modules, via the `kubernetes` and `local-kubernetes` providers. This guide shows you how to configure and use 3rd-party (or otherwise external) Helm charts, as well as your own charts in your Garden project. We also go through how to set up tests, tasks and hot-reloading for your charts.
 
-In this guide we'll be using the [vote-helm](https://github.com/garden-io/garden/tree/0.12.70/examples/vote-helm) project. If you prefer to just check out a complete example, the project itself is also a good resource.
+In this guide we'll be using the [vote-helm](https://github.com/garden-io/garden/tree/0.12.71/examples/vote-helm) project. If you prefer to just check out a complete example, the project itself is also a good resource.
 
 You may also want to check out the full [helm module reference](../../reference/module-types/helm.md).
 
 _Note: If you only need a way to deploy some Kubernetes manifests and don't need all the features of Helm, you can_
 _use the simpler `kubernetes` module type instead. Check out the_
-_[kubernetes-module](https://github.com/garden-io/garden/tree/0.12.70/examples/kubernetes-module) example for more info._
+_[kubernetes-module](https://github.com/garden-io/garden/tree/0.12.71/examples/kubernetes-module) example for more info._
 
 ## Basics
 
@@ -315,7 +315,7 @@ You can define a remote environment as a `production` environment by setting the
 
 ## Next steps
 
-Check out the full [helm module reference](../../reference/module-types/helm.md) for more details, and the [vote-helm](https://github.com/garden-io/garden/tree/0.12.70/examples/vote-helm) example project for a full project that showcases Garden's Helm support.
+Check out the full [helm module reference](../../reference/module-types/helm.md) for more details, and the [vote-helm](https://github.com/garden-io/garden/tree/0.12.71/examples/vote-helm) example project for a full project that showcases Garden's Helm support.
 
 Also check out the [Kubernetes module](./kubernetes.md)
 example for a simpler alternative, if you don't need all the features of Helm.

docs/k8s-plugins/remote-k8s/ingress-and-dns.md

@@ -5,7 +5,7 @@ order: 3
 
 # 3. Set Up Ingress, TLS and DNS
 
-By default, Garden will not install an ingress controller for remote environments. This can be toggled by setting the [`setupIngressController` flag](../../reference/providers/kubernetes.md#providerssetupingresscontroller) to `nginx`. Alternatively, you can set up your own ingress controller, e.g. using [Traefik](https://traefik.io/), [Ambassador](https://www.getambassador.io/) or [Istio](https://istio.io/). You can find an example for [using Garden with Istio](https://github.com/garden-io/garden/tree/0.12.70/examples/istio) in our [examples directory](https://github.com/garden-io/garden/tree/0.12.70/examples).
+By default, Garden will not install an ingress controller for remote environments. This can be toggled by setting the [`setupIngressController` flag](../../reference/providers/kubernetes.md#providerssetupingresscontroller) to `nginx`. Alternatively, you can set up your own ingress controller, e.g. using [Traefik](https://traefik.io/), [Ambassador](https://www.getambassador.io/) or [Istio](https://istio.io/). You can find an example for [using Garden with Istio](https://github.com/garden-io/garden/tree/0.12.71/examples/istio) in our [examples directory](https://github.com/garden-io/garden/tree/0.12.71/examples).
 
 You'll also need to point one or more DNS entries to your cluster, and configure a TLS certificate for the hostnames
 you will expose for ingress.

docs/misc/faq.md

@@ -45,7 +45,7 @@ You can also deploy `kubernetes` and `helm` modules to their own namespaces.
 
 ### How do I share code between modules?
 
-You can use the [copy directive](https://docs.garden.io/v/acorn-0.12/reference/module-types/container#build-dependencies-copy) of the `build.dependencies[]` field for that. See e.g. [this example project](https://github.com/garden-io/garden/tree/0.12.70/examples/build-dependencies).
+You can use the [copy directive](https://docs.garden.io/v/acorn-0.12/reference/module-types/container#build-dependencies-copy) of the `build.dependencies[]` field for that. See e.g. [this example project](https://github.com/garden-io/garden/tree/0.12.71/examples/build-dependencies).
 
 Alternatively you can hoist your `garden.yml` file so that it is at the same level or parent to all relevant build context and use the `include` field.
 
@@ -65,7 +65,7 @@ Use the [`targetImage` field](https://docs.garden.io/v/acorn-0.12/reference/modu
 
 ### How do I use base images?
 
-See [this example project](https://github.com/garden-io/garden/tree/0.12.70/examples/base-image).
+See [this example project](https://github.com/garden-io/garden/tree/0.12.71/examples/base-image).
 
 ### Can I use runtime variables in container builds (e.g. from tasks)?
 
@@ -111,11 +111,11 @@ include: [frontend/**/*]
 
 Note that you can put multiple Garden configuration files in the same directory, e.g. `project.garden.yml`, `api.garden.yml` and `frontend.garden.yml`.
 
-If you need the Dockerfile outside of the module root because you want to share it with other modules, you should consider having a single base image instead and then let each module have its own Dockerfile that's built on the base image. See the [base image example project](https://github.com/garden-io/garden/tree/0.12.70/examples/base-image) for an example of this.
+If you need the Dockerfile outside of the module root because you want to share it with other modules, you should consider having a single base image instead and then let each module have its own Dockerfile that's built on the base image. See the [base image example project](https://github.com/garden-io/garden/tree/0.12.71/examples/base-image) for an example of this.
 
 ### How do I include files/dirs (e.g. shared libraries) from outside the module root with the build context?
 
-See [this example project](https://github.com/garden-io/garden/tree/0.12.70/examples/build-dependencies).
+See [this example project](https://github.com/garden-io/garden/tree/0.12.71/examples/build-dependencies).
 
 ### How do I add Docker specific flags to the build command?
 
@@ -129,7 +129,7 @@ You can use the `dockerfile` field. For example:
 dockerfile: "${environment.name == 'prod' ? Dockerfile.prod : Dockerfile.dev}"
 ```
 
-See also the [base image example project](https://github.com/garden-io/garden/tree/0.12.70/examples/base-image) for an example of this.
+See also the [base image example project](https://github.com/garden-io/garden/tree/0.12.71/examples/base-image) for an example of this.
 
 ## Remote Building
 

docs/other-plugins/exec.md

@@ -99,7 +99,7 @@ services:
     env: ${modules.frontend.env} # <--- Reference the env variable defined above
 ```
 
-See also this [example project](https://github.com/garden-io/garden/tree/0.12.70/examples/local-service).
+See also this [example project](https://github.com/garden-io/garden/tree/0.12.71/examples/local-service).
 
 ## Next Steps
 

docs/pulumi-plugin/about.md

@@ -82,7 +82,7 @@ garden plugins pulumi preview -- my-pulumi-module my-other-pulumi-module
 
 ## Next steps
 
-Check out the [`pulumi` example](https://github.com/garden-io/garden/tree/0.12.70/examples/pulumi) project.
+Check out the [`pulumi` example](https://github.com/garden-io/garden/tree/0.12.71/examples/pulumi) project.
 
 Also take a look at the [pulumi provider reference](https://docs.garden.io/v/acorn-0.12/reference/providers/pulumi) and the [pulumi module type reference](https://docs.garden.io/v/acorn-0.12/reference/module-types/pulumi) for details on all the configuration parameters.
 

docs/reference/module-types/jib-container.md

@@ -7,7 +7,7 @@ tocTitle: "`jib-container`"
 
 ## Description
 
-Extends the [container module type](./container.md) to build the image with [Jib](https://github.com/GoogleContainerTools/jib). Use this to efficiently build container images for Java services. Check out the [jib example](https://github.com/garden-io/garden/tree/0.12.70/examples/jib-container) to see it in action.
+Extends the [container module type](./container.md) to build the image with [Jib](https://github.com/GoogleContainerTools/jib). Use this to efficiently build container images for Java services. Check out the [jib example](https://github.com/garden-io/garden/tree/0.12.71/examples/jib-container) to see it in action.
 
 The image is always built locally, directly from the module source directory (see the note on that below), before shipping the container image to the right place. You can set `build.tarOnly: true` to only build the image as a tarball.
 

docs/reference/providers/conftest-kubernetes.md

@@ -14,7 +14,7 @@ Simply add this provider to your project configuration, and configure your polic
 reference for how to configure default policies, default namespaces, and test failure thresholds for the generated
 modules.
 
-See the [conftest example project](https://github.com/garden-io/garden/tree/0.12.70/examples/conftest) for a simple
+See the [conftest example project](https://github.com/garden-io/garden/tree/0.12.71/examples/conftest) for a simple
 usage example.
 
 Below is the full schema reference for the provider configuration. For an introduction to configuring a Garden project with providers, please look at our [configuration guide](../../using-garden/configuration-overview.md).

docs/reference/providers/conftest.md

@@ -9,7 +9,7 @@ tocTitle: "`conftest`"
 
 This provider allows you to validate your configuration files against policies that you specify, using the [conftest tool](https://github.com/instrumenta/conftest) and Open Policy Agent rego query files. The provider creates a module type of the same name, which allows you to specify files to validate. Each module then creates a Garden test that becomes part of your Stack Graph.
 
-Note that, in many cases, you'll actually want to use more specific providers that can automatically configure your `conftest` modules, e.g. the [`conftest-container`](../module-types/conftest.md) and/or [`conftest-kubernetes`](../module-types/conftest.md) providers. See the [conftest example project](https://github.com/garden-io/garden/tree/0.12.70/examples/conftest) for a simple usage example of the latter.
+Note that, in many cases, you'll actually want to use more specific providers that can automatically configure your `conftest` modules, e.g. the [`conftest-container`](../module-types/conftest.md) and/or [`conftest-kubernetes`](../module-types/conftest.md) providers. See the [conftest example project](https://github.com/garden-io/garden/tree/0.12.71/examples/conftest) for a simple usage example of the latter.
 
 If those don't match your needs, you can use this provider directly and manually configure your `conftest` modules. Simply add this provider to your project configuration, and see the [conftest module documentation](../module-types/conftest.md) for a detailed reference. Also, check out the below reference for how to configure default policies, default namespaces, and test failure thresholds for all `conftest` modules.