Skip to content

Releases: garden-io/garden

0.14.11

28 Nov 12:17
@eysi09 eysi09
0.14.11
cc6506f

Choose a tag to compare

View all tags
0.14.11 Latest
Latest

Garden 0.14.11 is out! 🎉

This is a maintenance release that addresses some minor issues with the Garden 0.14.10 release. Check out the release notes for that one to learn more about the latest features.

Assets

Download the Garden binary for your platform from below or simply run garden self-update if you already have it installed.

Changelog

0.14.11 (2025-11-28)

Bug Fixes

  • secrets: bad error message when missing a secret in v2 backend (#7850) (32f03d327)

Improvements

Assets 14

edge-cedar

11 Mar 10:33
@stefreak stefreak
edge-cedar
6aaa139
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
edge-cedar Pre-release
Pre-release

This is an automatic build of Garden 0.14 (Cedar).

Note: This is not a stable release

Loading

0.14.10

26 Nov 17:55
@eysi09 eysi09
0.14.10
992551e

Choose a tag to compare

View all tags
0.14.10

Garden 0.14.10 is out! 🎉

This release contains a variety of new features and improvements, along with a handful of bug fixes and security updates. Below are some of the key additions.

Assets

Download the Garden binary for your platform from below or simply run garden self-update if you already have it installed.

Highlights

Automatic Environment Cleanup (”AEC”) for Kubernetes

We’ve implemented a new version of the AEC feature for Kubernetes, previously only available to Garden Enterprise customers.

With this, you can configure your Kubernetes namespaces to be automatically paused and/or cleaned up based on your preferences, on fixed schedules (e.g. every Friday at 8pm), or after X many hours or days since the environment was last updated, or any combination thereof. This is particularly useful for ephemeral dev and PR preview environments, which can easily add up in costs over time.

Please see the Automatic Environment Cleanup guide for details on how it works and how to use it.

Requires Garden Cloud (any subscription tier)

Cloud Variables and Secrets

Another feature previously only available in Garden Enterprise, now available to all Garden Cloud users, and with more flexibility than previously. You can now define lists of variables and secrets in Garden Cloud and use them in your Garden projects. Each variable or secret can optionally be scoped to individual environment types or users. New in this release is the ability to use the same variables across multiple Garden projects (which has been requested by several users).

Please see the Remote Variables and Secrets guide for details on how to set this up and use it in your projects.

remote-variables

Requires Garden Cloud (any subscription tier)

Command history and activity in Garden Cloud

Also previously only available in Garden Enterprise, we now gather a history of executed commands along with detailed action results and logs, all neatly organized in the Garden Cloud UI.

You can opt out of this (and still use Garden Cloud for other things) by setting GARDEN_DISABLE_CLOUD_LOGS=1 in your shell environment or pipelines, or by adding disableCloudLogs: true to your Project configuration.

Screenshot 2025-11-25 at 17 37 33

Requires Garden Cloud (any subscription tier)

Log output changes and improvements

Based on user feedback, we’ve decided to make the default log level for Garden commands verbose (instead of info). This means you’ll see more details by default when running CLI commands, such as container build logs, action execution logs etc.

To revert to the previous behavior, you can always set --log-level=info (or -l=2) in your Garden CLI commands or set GARDEN_LOG_LEVEL=info in your shell environment.

We’ve also added better progress output during execution along with a short summary at the end, to better identify which actions are running, pending, what failed, succeeded etc.

Changelog

Features

Improvements

Bug Fixes

  • container: don't check for local docker if using cloud builder (#7813) (5d0d4dffe)
  • core: do not log "helm get manifest" output (#7795) (5638647fe)
  • diff: some false positives in diff command (#7806) (d306e66ca)
  • k8s: error when re-deploying failed StatefulSet or DaemonSet (#7798) (fa99ce8c0)
Loading

edge-bonsai

01 Feb 18:23
@stefreak stefreak
edge-bonsai
4efddf5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
edge-bonsai Pre-release
Pre-release

This is an automatic build of Garden 0.13 (Bonsai).

Note: This is not a stable release

Loading

0.14.9

30 Sep 20:14
@eysi09 eysi09
0.14.9
5e1a1bc

Choose a tag to compare

View all tags
0.14.9

Garden 0.14.9 is out! 🎉

This release includes features, bug fixes and various improvements. We'll highlight the big ones below and you'll find the full list further down.

Assets

Download the Garden binary for your platform from below or simply run garden self-update if you already have it installed.

Highlights

Matrix templates

A major new capability is "matrix templates" which has been widely requested and allows users to create multiple parameterized instances of actions, for example for splitting test suites into segments.

Here's a quick peak at how a RenderTemplate kind can generate four Build actions:

kind: RenderTemplate
name: dist
template: dist
matrix:
  os: ["linux", "macos"]
  arch: ["amd64", "arm64"]

Another config template improvement is that inputs can now be defined in YAML as opposed to requiring a JSON schema. For example:

kind: ConfigTemplate
name: dist

inputs:
  os:
    type: string
  arch:
    type: string

You can learn more in our docs.

Module-based services and tasks can now depend on Deploy+Run actions

Another quality of life improvement is support for having module-based services and tasks depend on Deploy and Run actions. Before this, actions could depend on modules but not the other way around. This change should make it easier to incrementally adopt actions while leaving some modules around.

Changelog

0.14.9 (2025-09-30)

Features

  • allow module-based services+tasks to depend on Deploy+Run actions (#7730) (ae0e5e7cc)
  • core: add version.excludeFiles field (#7689) (8715b59e2)
  • template: support matrix actions via RenderTemplate (#7725) (2acbc68cb)

Bug Fixes

  • cloudbuild: attempt to prevent uncaught exception crash during build (#7713) (cd93902b7)
  • container: one more safeguard to prevent EPIPE error (#7720) (a2f55a85a)
  • core: only send valid JSON lines to progressui (#7732) (d3f2d2662)
  • k8s: don't log tar availability check output to console (#7719) (60beac713)

Improvements

  • default to include:[] for container Deploy/Test/Run actions (#7717) (525c89c48)
  • container: better error handling in docker build logs (#7724) (da09b1705)
  • container: use updated and more resilient buildkit log parser (#7716) (04f89541a)
  • k8s: support interactive mode on kubernetes-exec Test actions (#7714) (9b9ba1d6e)
Loading

0.14.8

08 Sep 11:54
@eysi09 eysi09
0.14.8
6a74268

Choose a tag to compare

View all tags
0.14.8

Garden 0.14.8 is out! 🎉

This release adds several new features, geared towards achieving more efficient graph execution and better caching through version controls:

  • A new garden diff command, which can help troubleshoot and understand effects of changes between branches/commits and/or between different environments, effects of overriding specific variables etc. Run garden diff --help for a more detailed explanation.
  • Adding to the last release's new version.excludeValues  and version.excludeFields fields on all actions, you now have a new version.excludeDependencies field as well as a project level excludeValuesFromActionVersions field. For details see the references (here)[https://docs.garden.io/edge-release/reference/action-types/test/container#version.excludedependencies] and (here)[https://docs.garden.io/edge-release/reference/project-config#excludevaluesfromactionversions], respectively.
  • exec actions can now expose outputs to be referenced by other actions. See the reference (here)[https://docs.garden.io/edge-release/reference/action-types/run/exec#spec.command] for example. This works across all exec action kinds.
  • exec actions now all have a spec.statusCommand field. You can use this to avoid unnecessary repetition of exec actions. See the reference (here)[https://docs.garden.io/edge-release/reference/action-types/run/exec#spec.statuscommand] for example.

Many thanks to @okuuva for the contribution to this release!

Assets

Download the Garden binary for your platform from below or simply run garden self-update if you already have it installed.

Changelog

0.14.8 (2025-09-06)

Bug Fixes

Features

  • garden diff command, to compare action versions between branches/commits (#7670) (2e199400b)
  • config: add version.excludeDependencies to action config (#7658) (6f22a5c67)
  • config: add project-level excludeValuesFromActionVersions field (#7653) (3fc5f48b7)
  • exec: support arbitratry outputs from exec actions (#7630) (908111bc2)
  • exec: add statusCommand for more efficient exec Build/Test/Run actions (#7629) (9749b8cc3)

Fixed Issues

Contributors

okuuva
Loading

0.14.7

13 Aug 13:47
@gordon-garden-bot gordon-garden-bot
0.14.7
a0e8c31

Choose a tag to compare

View all tags
0.14.7

Garden 0.14.7 is out! 🎉

This release introduces version exclusion features that can make it much easier to achieve cache hits for test actions with runtime dependencies. For more details, refer to the reference docs for the new version.excludeValues and version.excludeFields action-level fields, which are now available on all action kinds and types.

We also fix a template string bug in the $merge operator when resolving cross-references within the same variable scope, and a regression in the dev command from the last release.

Assets

Download the Garden binary for your platform from below or simply run garden self-update if you already have it installed.

Changelog

Features

  • config: add version.excludeFields to exclude config fields from… (#7579) (c9ded5ce2)
  • config: add version.excludeValues to action configs (#7572) (349f689b3)

Bug Fixes

  • improve error message on 5xx errors (#7534) (7fb3c025d)
  • template: do not throw circular reference error when resolving cross-references in the same scope (#7550) (8b6509ccf)
Loading

0.13.62

13 Aug 14:18
@gordon-garden-bot gordon-garden-bot
0.13.62
f7e42bf

Choose a tag to compare

View all tags
0.13.62

Garden 0.13.62 is out! 🎉

This is a maintenance release that fixes a template string bug in the $merge operator when resolving cross-references within the same variable scope.

Assets

Download the Garden binary for your platform from below or simply run garden self-update 0.13.62 if you already have it installed.

Changelog

Bug Fixes

  • template: do not throw circular reference error when resolving cross-references in the same scope (#7595) (c295f7c7c)
Loading

0.14.6

30 Jul 17:25
@gordon-garden-bot gordon-garden-bot
0.14.6
5bcc958

Choose a tag to compare

View all tags
0.14.6

Garden 0.14.6 is out! 🎉

This release fixes a bug in templated modules, and adds a command for the Kubernetes plugin to scale workloads to zero.

Assets

Download the Garden binary for your platform from below or simply run garden self-update if you already have it installed.

Changelog

Bug Fixes

  • templates: incorrect path resolution for templated modules (#7529) (b197775a6)

Features

  • k8s: add pause command to scale workloads to zero (#7505) (cf7b78a97)
Loading

0.13.61

30 Jul 17:57
@gordon-garden-bot gordon-garden-bot
0.13.61
fa5b151

Choose a tag to compare

View all tags
0.13.61

Garden 0.13.61 is out! 🎉

This is a small release to fix a bug in module templates.

Assets

Download the Garden binary for your platform from below or simply run garden self-update 0.13.61 if you already have it installed.

Changelog

Bug Fixes

  • templates: incorrect path resolution for templated modules (#7529) (b0776e2d2)
Loading