chore(release): bump version to 0.14.11

eysi09 · eysi09 · commit cc6506fee0aa · 2025-11-28T11:55:48.000+01:00
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,4 +1,16 @@
 
+<a name="0.14.11"></a>
+## [0.14.11](https://github.com/garden-io/garden/compare/0.14.10...0.14.11) (2025-11-28)
+
+### Bug Fixes
+
+* **cloud:** default list for var utility commands ([#7849](https://github.com/garden-io/garden/issues/7849)) ([ed6e891ed](https://github.com/garden-io/garden/commit/ed6e891ed))
+* **secrets:** bad error message when missing a secret in v2 backend ([#7850](https://github.com/garden-io/garden/issues/7850)) ([32f03d327](https://github.com/garden-io/garden/commit/32f03d327))
+
+### Improvements
+
+* **cloud:** default orgs ([#7852](https://github.com/garden-io/garden/issues/7852)) ([6aaa13972](https://github.com/garden-io/garden/commit/6aaa13972))
+
 <a name="0.14.10"></a>
 ## [0.14.10](https://github.com/garden-io/garden/compare/0.14.9...0.14.10) (2025-11-26)
 
diff --git a/README.md b/README.md
@@ -16,7 +16,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.14.10/examples">Examples</a>
+  <a href="https://github.com/garden-io/garden/tree/0.14.11/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>
diff --git a/cli/package.json b/cli/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@garden-io/cli",
-  "version": "0.14.10",
+  "version": "0.14.11",
   "description": "Cloud native testing platform for testing and developing container applications on Kubernetes",
   "type": "module",
   "repository": {
diff --git a/core/package.json b/core/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@garden-io/core",
-  "version": "0.14.10",
+  "version": "0.14.11",
   "description": "A full-featured development framework for containers and serverless",
   "type": "module",
   "repository": {
diff --git a/docs/garden-for/kubernetes/deploy-k8s-resource.md b/docs/garden-for/kubernetes/deploy-k8s-resource.md
@@ -230,7 +230,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.14.10/examples/k8s-deploy-patch-resources) using this approach.
+Here's a [complete example project](https://github.com/garden-io/garden/tree/0.14.11/examples/k8s-deploy-patch-resources) using this approach.
 
 ### Option 2: Using Garden template strings
 
diff --git a/docs/garden-for/terraform/README.md b/docs/garden-for/terraform/README.md
@@ -13,7 +13,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.14.10/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.14.11/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.
 
@@ -56,5 +56,5 @@ multiple AWS labmdas that should each have their own stack), check out [the Terr
 ## Next steps
 
 Check out how to configure the Terraform provider and/or actions in the following pages.
-You'll find some [Terraform examples here](https://github.com/garden-io/garden/tree/0.14.10/examples).
+You'll find some [Terraform examples here](https://github.com/garden-io/garden/tree/0.14.11/examples).
 
diff --git a/docs/garden-for/terraform/configure-provider.md b/docs/garden-for/terraform/configure-provider.md
@@ -15,7 +15,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.14.10/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.14.11/examples/terraform-gke):
 
 ```yaml
 apiVersion: garden.io/v2
diff --git a/docs/guides/using-garden-in-circleci.md b/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.14.10/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.14.11/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.
 
diff --git a/docs/overview/use-cases/jumpstart-idp.md b/docs/overview/use-cases/jumpstart-idp.md
@@ -38,6 +38,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.14.10/examples/remote-sources)
+- [Remote sources example project](https://github.com/garden-io/garden/tree/0.14.11/examples/remote-sources)
 
-- [kubernetes Deploy action type example with config templates](https://github.com/garden-io/garden/tree/0.14.10/examples/k8s-deploy-config-templates)
+- [kubernetes Deploy action type example with config templates](https://github.com/garden-io/garden/tree/0.14.11/examples/k8s-deploy-config-templates)
diff --git a/docs/overview/use-cases/local-development-remote-clusters.md b/docs/overview/use-cases/local-development-remote-clusters.md
@@ -59,4 +59,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.14.10/examples/k8s-deploy-patch-resources)
+- [Kubernetes Deploy action example project](https://github.com/garden-io/garden/tree/0.14.11/examples/k8s-deploy-patch-resources)
diff --git a/docs/overview/use-cases/on-demand-preview-envs.md b/docs/overview/use-cases/on-demand-preview-envs.md
@@ -59,4 +59,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.14.10/examples/k8s-deploy-patch-resources)
+- [Kubernetes Deploy action example project](https://github.com/garden-io/garden/tree/0.14.11/examples/k8s-deploy-patch-resources)
diff --git a/docs/reference/action-types/Build/jib-container.md b/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.14.10/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.14.11/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.
 
diff --git a/docs/reference/module-types/jib-container.md b/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.14.10/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.14.11/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.
 
diff --git a/docs/reference/providers/jib.md b/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.14.10/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.14.11/examples/jib-container) to see it in action.
 
 Below is the full schema reference for the provider configuration..
 
diff --git a/docs/tutorials/remote-k8s/ingress-and-dns.md b/docs/tutorials/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.14.10/examples/istio) in our [examples directory](https://github.com/garden-io/garden/tree/0.14.10/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.14.11/examples/istio) in our [examples directory](https://github.com/garden-io/garden/tree/0.14.11/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.
diff --git a/e2e/package.json b/e2e/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@garden-io/e2e",
-  "version": "0.14.10",
+  "version": "0.14.11",
   "description": "End-to-end tests for the Garden CLI",
   "type": "module",
   "repository": {
diff --git a/package.json b/package.json
@@ -6,7 +6,7 @@
     "type": "git",
     "url": "git+https://github.com/garden-io/garden.git"
   },
-  "version": "0.14.10",
+  "version": "0.14.11",
   "author": "Garden Technologies, Inc. <info@garden.io>",
   "license": "MPL-2.0",
   "homepage": "https://github.com/garden-io/garden",
diff --git a/plugins/jib/package.json b/plugins/jib/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@garden-io/garden-jib",
-  "version": "0.14.10",
+  "version": "0.14.11",
   "description": "Jib container plugin for Garden",
   "type": "module",
   "main": "build/src/index.js",
diff --git a/plugins/pulumi/package.json b/plugins/pulumi/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@garden-io/garden-pulumi",
-  "version": "0.14.10",
+  "version": "0.14.11",
   "description": "Pulumi plugin for Garden",
   "type": "module",
   "main": "build/src/index.js",
diff --git a/plugins/terraform/package.json b/plugins/terraform/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@garden-io/garden-terraform",
-  "version": "0.14.10",
+  "version": "0.14.11",
   "description": "Terraform plugin for Garden",
   "type": "module",
   "main": "build/src/index.js",
diff --git a/sdk/package.json b/sdk/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@garden-io/sdk",
-  "version": "0.14.10",
+  "version": "0.14.11",
   "description": "TypeScript plugin SDK for Garden",
   "type": "module",
   "repository": {

Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,6 @@`
`1`	`1`	`{`
`2`	`2`	`"name": "@garden-io/cli",`
`3`		`- "version": "0.14.10",`
	`3`	`+ "version": "0.14.11",`
`4`	`4`	`"description": "Cloud native testing platform for testing and developing container applications on Kubernetes",`
`5`	`5`	`"type": "module",`
`6`	`6`	`"repository": {`
Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,6 @@`
`1`	`1`	`{`
`2`	`2`	`"name": "@garden-io/core",`
`3`		`- "version": "0.14.10",`
	`3`	`+ "version": "0.14.11",`
`4`	`4`	`"description": "A full-featured development framework for containers and serverless",`
`5`	`5`	`"type": "module",`
`6`	`6`	`"repository": {`
Original file line number	Diff line number	Diff line change
`@@ -59,4 +59,4 @@ Join our [Discord community](https://go.garden.io/discord) 🌸 for access to Ga`
`59`	`59`
`60`	`60`	`## Examples`
`61`	`61`
`62`		`-- [Kubernetes Deploy action example project](https://github.com/garden-io/garden/tree/0.14.10/examples/k8s-deploy-patch-resources)`
	`62`	`+- [Kubernetes Deploy action example project](https://github.com/garden-io/garden/tree/0.14.11/examples/k8s-deploy-patch-resources)`