chore(release): bump version to 0.13.43 (#6609)

* chore(release): bump version to 0.13.43

* chore: bump version in package-lock.json

* chore: amend the changelog

Delete the commit, that was reverted, from the list of bug fixes.

CHANGELOG.md

@@ -1,4 +1,33 @@
 
+<a name="0.13.43"></a>
+## [0.13.43](https://github.com/garden-io/garden/compare/0.13.42...0.13.43) (2024-10-30)
+
+### Bug Fixes
+
+* correct deploy action validation in container plugin extension ([#6606](https://github.com/garden-io/garden/issues/6606)) ([ba2a4954a](https://github.com/garden-io/garden/commit/ba2a4954a))
+* render action reference in error message ([#6605](https://github.com/garden-io/garden/issues/6605)) ([4ebe9975a](https://github.com/garden-io/garden/commit/4ebe9975a))
+* **k8s:** correctly set image pull secret on sync pod ([#6533](https://github.com/garden-io/garden/issues/6533)) ([a2826a947](https://github.com/garden-io/garden/commit/a2826a947))
+* **k8s:** add imagePullSecret from kubernetes provider to sync init container ([#6530](https://github.com/garden-io/garden/issues/6530)) ([07a577ef4](https://github.com/garden-io/garden/commit/07a577ef4))
+* **profiler:** fix sync profiler and collect more data ([#6586](https://github.com/garden-io/garden/issues/6586)) ([04dcc006c](https://github.com/garden-io/garden/commit/04dcc006c))
+* **pulumi:** stack not being selected before getting outputs when autoApply = false ([#6554](https://github.com/garden-io/garden/issues/6554)) ([8fd42f3b3](https://github.com/garden-io/garden/commit/8fd42f3b3))
+* **pulumi:** prevent existing pulumi configs from being overwritten ([#6526](https://github.com/garden-io/garden/issues/6526)) ([dcfef40c6](https://github.com/garden-io/garden/commit/dcfef40c6))
+
+### Features
+
+* **exec:** separate `stdout` and `stderr` in Run and Test `exec`-action outputs ([#6572](https://github.com/garden-io/garden/issues/6572)) ([5a04f60ac](https://github.com/garden-io/garden/commit/5a04f60ac))
+* **k8s:** allow using registry mirror for utility images ([#6552](https://github.com/garden-io/garden/issues/6552)) ([122371dd6](https://github.com/garden-io/garden/commit/122371dd6))
+* **pulumi:** add `spec.showSecretsInOutput` config to Pulumi deploy action ([#6555](https://github.com/garden-io/garden/issues/6555)) ([682e37896](https://github.com/garden-io/garden/commit/682e37896))
+
+### Improvements
+
+* make sure artifacts are always fetched ([#6532](https://github.com/garden-io/garden/issues/6532)) ([593c9cbdf](https://github.com/garden-io/garden/commit/593c9cbdf))
+* **api:** send action type to cloud ([#5447](https://github.com/garden-io/garden/issues/5447)) ([15fe97404](https://github.com/garden-io/garden/commit/15fe97404))
+
+### Performance Improvements
+
+* optimize action configs processing ([#6547](https://github.com/garden-io/garden/issues/6547)) ([af6df50a8](https://github.com/garden-io/garden/commit/af6df50a8))
+* **git:** use `sub-tree` scan mode for config files scan ([#6483](https://github.com/garden-io/garden/issues/6483)) ([131663140](https://github.com/garden-io/garden/commit/131663140))
+
 <a name="0.13.42"></a>
 ## [0.13.42](https://github.com/garden-io/garden/compare/0.13.41...0.13.42) (2024-10-08)
 

README.md

@@ -19,7 +19,7 @@ _If you love Garden, please ★ star this repository to show your support :green
   <span>&nbsp;&nbsp;•&nbsp;&nbsp;</span>
   <a href="https://docs.garden.io/?utm_source=github">Docs</a>
   <span>&nbsp;&nbsp;•&nbsp;&nbsp;</span>
-  <a href="https://github.com/garden-io/garden/tree/0.13.42/examples">Examples</a>
+  <a href="https://github.com/garden-io/garden/tree/0.13.43/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.13.42",
+  "version": "0.13.43",
   "description": "Cloud native testing platform for testing and developing container applications on Kubernetes",
   "type": "module",
   "repository": {

core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@garden-io/core",
-  "version": "0.13.42",
+  "version": "0.13.43",
   "description": "A full-featured development framework for containers and serverless",
   "type": "module",
   "repository": {
@@ -274,4 +274,4 @@
     "fsevents": "^2.3.3"
   },
   "gitHead": "b0647221a4d2ff06952bae58000b104215aed922"
-}
+}

docs/getting-started/quickstart.md

@@ -111,6 +111,6 @@ If you'd like to better understand how a Garden project is configured, we recomm
 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 referencing our [example
-projects on GitHub](https://github.com/garden-io/garden/tree/0.13.42/examples) and the section of our docs title [Using Garden](../using-garden/configuration-overview.md), which covers all parts of Garden in detail.
+projects on GitHub](https://github.com/garden-io/garden/tree/0.13.43/examples) and the section of our docs title [Using Garden](../using-garden/configuration-overview.md), which covers all parts of Garden in detail.
 
 If you have any questions or feedback—or just want to say hi 🙂—we encourage you to join our [Discord community](https://go.garden.io/discord)!

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

@@ -11,7 +11,7 @@ For the purposes of this example we'll be using [CircleCI](https://circleci.com)
 
 ## Project overview
 
-The project is based on our basic [demo-project](https://github.com/garden-io/garden/tree/0.13.42/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.13.43/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/actions/deploy/kubernetes.md

@@ -228,7 +228,7 @@ spec:
 
 With this approach, you can add the Garden action to your project without making any changes to existing config.
 
-Here's a [complete example project](https://github.com/garden-io/garden/tree/0.13.42/examples/k8s-deploy-patch-resources) using this approach.
+Here's a [complete example project](https://github.com/garden-io/garden/tree/0.13.43/examples/k8s-deploy-patch-resources) using this approach.
 
 ### Option 2: Using Garden template strings
 
@@ -259,7 +259,7 @@ spec:
           image: ${actions.build.api.outputs.deployment-image-id} # <--- Garden will resolve this to the correct image before applying the manifest
 ```
 
-Here's a [complete example](https://github.com/garden-io/garden/tree/0.13.42/examples/k8s-deploy-shared-manifests) using this approach. The downside though is that this is no longer a valid Kubernetes manifest.
+Here's a [complete example](https://github.com/garden-io/garden/tree/0.13.43/examples/k8s-deploy-shared-manifests) using this approach. The downside though is that this is no longer a valid Kubernetes manifest.
 
 Similarly, if you define your manifest inline you can set the image like so:
 

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.13.42/examples/istio) in our [examples directory](https://github.com/garden-io/garden/tree/0.13.42/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.13.43/examples/istio) in our [examples directory](https://github.com/garden-io/garden/tree/0.13.43/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/reference/action-types/Build/jib-container.md

@@ -7,7 +7,7 @@ tocTitle: "`jib-container` Build"
 
 ## Description
 
-Extends the [container 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.13.42/examples/jib-container) to see it in action.
+Extends the [container 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.13.43/examples/jib-container) to see it in action.
 
 The image is always built locally, directly from the 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/module-types/jib-container.md

@@ -11,7 +11,7 @@ Modules are deprecated and will be removed in version `0.14`. Please use [action
 
 ## Description
 
-Extends the [container 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.13.42/examples/jib-container) to see it in action.
+Extends the [container 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.13.43/examples/jib-container) to see it in action.
 
 The image is always built locally, directly from the 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
 actions.
 
-See the [conftest example project](https://github.com/garden-io/garden/tree/0.13.42/examples/conftest) for a simple
+See the [conftest example project](https://github.com/garden-io/garden/tree/0.13.43/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/open-policy-agent/conftest) and Open Policy Agent rego query files. The provider creates Test action types of the same name, which allow you to specify files to validate.
 
-Note that, in many cases, you'll actually want to use more specific providers that can automatically configure your `conftest` actions, e.g. the [`conftest-container`](./conftest-container.md) and/or [`conftest-kubernetes`](./conftest-kubernetes.md) providers. See the [conftest example project](https://github.com/garden-io/garden/tree/0.13.42/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` actions, e.g. the [`conftest-container`](./conftest-container.md) and/or [`conftest-kubernetes`](./conftest-kubernetes.md) providers. See the [conftest example project](https://github.com/garden-io/garden/tree/0.13.43/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` actions. Simply add this provider to your project configuration, and see the [conftest action documentation](../action-types/Test/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` actions.
 

docs/reference/providers/hadolint.md

@@ -11,7 +11,7 @@ This provider creates a [`hadolint`](../action-types/Test/hadolint.md) Test acti
 
 To configure `hadolint`, you can use `.hadolint.yaml` config files. For each Test, we first look for one in the relevant action's root. If none is found there, we check the project root, and if none is there we fall back to default configuration. Note that for reasons of portability, we do not fall back to global/user configuration files.
 
-See the [hadolint docs](https://github.com/hadolint/hadolint#configure) for details on how to configure it, and the [hadolint example project](https://github.com/garden-io/garden/tree/0.13.42/examples/hadolint) for a usage example.
+See the [hadolint docs](https://github.com/hadolint/hadolint#configure) for details on how to configure it, and the [hadolint example project](https://github.com/garden-io/garden/tree/0.13.43/examples/hadolint) for a 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/jib.md

@@ -11,7 +11,7 @@ tocTitle: "`jib`"
 
 Provides support for [Jib](https://github.com/GoogleContainerTools/jib) via the [jib action type](../action-types/Build/jib-container.md).
 
-Use this to efficiently build container images for Java services. Check out the [jib example](https://github.com/garden-io/garden/tree/0.13.42/examples/jib-container) to see it in action.
+Use this to efficiently build container images for Java services. Check out the [jib example](https://github.com/garden-io/garden/tree/0.13.43/examples/jib-container) to see it in action.
 
 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/terraform-plugin/about.md

@@ -15,7 +15,7 @@ Under the hood, Garden simply wraps Terraform, so there's no magic involved. Gar
 
 Terraform resources can be provisioned through the `terraform` provider when initializing Garden, or via `terraform` actions that are utilized like other actions in your stack.
 
-The former, having a single Terraform stack for your whole project, is most helpful if other provider configurations need to reference the outputs from your Terraform stack, or if most/all of your services depend on the infrastructure provisioned in your Terraform stack. A good example of this is the [terraform-gke example](https://github.com/garden-io/garden/tree/0.13.42/examples/terraform-gke) project, which provisions a GKE cluster that the `kubernetes` provider then runs on, along with the services in the project. The drawback is that Garden doesn't currently watch for changes in those Terraform files, and you need to restart to apply new changes, or apply them manually.
+The former, having a single Terraform stack for your whole project, is most helpful if other provider configurations need to reference the outputs from your Terraform stack, or if most/all of your services depend on the infrastructure provisioned in your Terraform stack. A good example of this is the [terraform-gke example](https://github.com/garden-io/garden/tree/0.13.43/examples/terraform-gke) project, which provisions a GKE cluster that the `kubernetes` provider then runs on, along with the services in the project. The drawback is that Garden doesn't currently watch for changes in those Terraform files, and you need to restart to apply new changes, or apply them manually.
 
 Using `terraform` _Deploy actions_, can be better if your other providers don't need to reference the stack outputs but other Deploy, Run and Test actions do. In this style, you can basically create small Terraform stacks that are part of your Stack Graph much like other services. A good example would be deploying a database instance, that other services in your project can then connect to.
 
@@ -87,6 +87,6 @@ Now when you deploy a new Terraformed environment, the new backend statefile wil
 
 ## Next steps
 
-Check out the [terraform-gke example](https://github.com/garden-io/garden/tree/0.13.42/examples/terraform-gke) project. Also take a look at the [Terraform provider reference](../reference/providers/terraform.md) and the [Terraform Deploy action type reference](../reference/action-types/Deploy/terraform.md) for details on all the configuration parameters.
+Check out the [terraform-gke example](https://github.com/garden-io/garden/tree/0.13.43/examples/terraform-gke) project. Also take a look at the [Terraform provider reference](../reference/providers/terraform.md) and the [Terraform Deploy action type reference](../reference/action-types/Deploy/terraform.md) for details on all the configuration parameters.
 
 If you're having issues with Terraform itself, please refer to the [official docs](https://developer.hashicorp.com/terraform/docs).

docs/terraform-plugin/configure-provider.md

@@ -17,7 +17,7 @@ providers:
   ...
 ```
 
-If you'd like to apply the stack when starting Garden, and then reference the stack outputs in other providers (or actions), you need to add a couple of more flags. Here's the project config from the aforementioned [terraform-gke example](https://github.com/garden-io/garden/tree/0.13.42/examples/terraform-gke):
+If you'd like to apply the stack when starting Garden, and then reference the stack outputs in other providers (or actions), you need to add a couple of more flags. Here's the project config from the aforementioned [terraform-gke example](https://github.com/garden-io/garden/tree/0.13.43/examples/terraform-gke):
 
 ```yaml
 apiVersion: garden.io/v1

docs/use-cases/jumpstart-idp.md

@@ -39,6 +39,6 @@ Join our [Discord community](https://go.garden.io/discord) 🌸 for access to Ga
 
 ## Examples
 
-- [Remote sources example project](https://github.com/garden-io/garden/tree/0.13.42/examples/remote-sources)
+- [Remote sources example project](https://github.com/garden-io/garden/tree/0.13.43/examples/remote-sources)
 
-- [kubernetes Deploy action type example with config templates](https://github.com/garden-io/garden/tree/0.13.42/examples/k8s-deploy-config-templates)
+- [kubernetes Deploy action type example with config templates](https://github.com/garden-io/garden/tree/0.13.43/examples/k8s-deploy-config-templates)

docs/use-cases/local-development-remote-clusters.md

@@ -61,5 +61,5 @@ Join our [Discord community](https://go.garden.io/discord) 🌸 for access to Ga
 
 ## Examples
 
-- [Kubernetes Deploy action example project](https://github.com/garden-io/garden/tree/0.13.42/examples/k8s-deploy-patch-resources)
-- [Local mode for `kubernetes` action type](https://github.com/garden-io/garden/tree/0.13.42/examples/local-mode-k8s)
+- [Kubernetes Deploy action example project](https://github.com/garden-io/garden/tree/0.13.43/examples/k8s-deploy-patch-resources)
+- [Local mode for `kubernetes` action type](https://github.com/garden-io/garden/tree/0.13.43/examples/local-mode-k8s)

docs/use-cases/on-demand-preview-envs.md

@@ -60,4 +60,4 @@ Join our [Discord community](https://go.garden.io/discord) 🌸 for access to Ga
 
 ## Examples
 
-- [Kubernetes Deploy action example project](https://github.com/garden-io/garden/tree/0.13.42/examples/k8s-deploy-patch-resources)
+- [Kubernetes Deploy action example project](https://github.com/garden-io/garden/tree/0.13.43/examples/k8s-deploy-patch-resources)

e2e/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@garden-io/e2e",
-  "version": "0.13.42",
+  "version": "0.13.43",
   "description": "End-to-end tests for the Garden CLI",
   "type": "module",
   "repository": {