0.12.56-0

chore(release): release 0.12.56-0

0.12.55

Garden 0.12.55 is out! 🎉

This follow-up patch release fixes the regression in project-level variables resolution introduced in 0.12.54.

Assets

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

• Garden v0.12.55 for Alpine AMD64 (tar.gz)
• Garden v0.12.55 for Linux AMD64 (tar.gz)
• Garden v0.12.55 for MacOS AMD64 (tar.gz)
• Garden v0.12.55 for Windows AMD64 (.zip)

Changelog

Features

• retry k8s api calls on ECONNREFUSED and 500 errors (64cdeabdb)

Bug Fixes

• revert: remove noProject flag from custom commands (016c5eab9)

0.12.55-0

chore(release): release 0.12.55-0

0.12.54

Garden 0.12.54 is out! 🎉

​
This is a maintenance release. It includes a few bug fixes, minor features, and improvements.
​
Many thanks to @i0na-k and @shumailxyz for the contributions 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.
​

• Garden v0.12.54 for Alpine AMD64 (tar.gz)
• Garden v0.12.54 for Linux AMD64 (tar.gz)
• Garden v0.12.54 for MacOS AMD64 (tar.gz)
• Garden v0.12.54 for Windows AMD64 (.zip)
  ​

Changelog

​

Bug Fixes

​

• use the correct secret in pullFromExternalRegistry in kaniko builds (#4094) (9b81a288a)
• docs: move pvc shared volumes info to the right page (1fdb7e087)
  ​

Features

​

• support pre-release versions in self-update command (#4022) (06e9e56a1)
  ​

Improvements

• more granular version control in self-update command (#3999) (9607b9219)
• add additional info to error message when sh is not found (#3980) (69d11b1fb)
• k8s: catch internal etcdserver throttling error from API (95d2108d1)
• logger: various fixes to make basic logger render nicer (96f6721fe)

0.12.54-0

chore(release): release 0.12.54-0

0.13.0-0

As of today, we’re putting Garden Bonsai (0.13) into beta!

Most of our docs haven’t been updated yet (we’ll be working on that in the coming days and weeks), but here’s a guide for migrating to Bonsai: https://docs.garden.io/v/bonsai-release/tutorials/migrating-to-bonsai

We also recommend having a look at the updated example projects for examples of action configs: https://github.com/garden-io/garden/tree/0.13/examples

Note for Garden Cloud users: We’re still making the needed changes to Cloud’s API to support Garden Bonsai, so you won’t have access to the full functionality of Cloud until those have been rolled out (which should be done in the next week or so).

Here are some of the highlights:

• Actions instead of modules: A new, more lightweight, more flexible and more powerful way to define your Stack Graph.
• Modules are now converted into actions internally, so this is backwards-compatible with 0.12.
• Any action can depend on any action: This means that e.g. Tests can depend on Builds.
• The new kubernetes-exec Run and Test action types introduce rebuild-free Tests and Runs.
  • This is great when running your tests while coding. Want to run your integ/e2e tests lightning fast without rebuilding? This is your jam.
• For Runs (known as tasks in 0.12), you can now also shave off a significant amount of time when spinning up your stack.
  • Example: If you need to run a script against your database after it’s deployed before it’s ready (e.g. to init a schema or load test data), you no longer need to spin up a one-off pod to do this.
    • Simply exec the command in the running service by adding a dependency on a kubernetes-exec Run that executes the script.
  • Also useful for simple scripts you want to run in your services (e.g. for generating DB migrations or refreshing your dev DB).
• Greatly improved logging, with more detail shown by default.
• An interactive dev command! garden dev now starts an interactive session where you can...
  • Start and stop code syncing for individual deployments with or without redeploying.
  • Run individual actions, e.g. Tests or Runs (a perfect combo with the new kubernetes-exec actions).
• Basically interactively access the whole Garden CLI without having to re-scan your project or init providers, making for a much snappier developer experience in total.

There’s more exciting stuff coming up in the following days and weeks, so stay tuned!

We’d love to hear your feedback and bug reports, so we can move to a general-availability release as soon as possible.

0.12.53

Garden 0.12.53 is out! 🎉

This is a follow-up patch release that improves the performance and reliability of builds, tasks and tests for some users.

Assets

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

• Garden v0.12.53 for Alpine AMD64 (tar.gz)
• Garden v0.12.53 for Linux AMD64 (tar.gz)
• Garden v0.12.53 for MacOS AMD64 (tar.gz)
• Garden v0.12.53 for Windows AMD64 (.zip)

Changelog

0.12.53 (2023-03-17)

Bug Fixes

• k8s: retry exec attempts in PodRunner (#3956) (5076ed58b)
• k8s: more stable & performant log streaming (#3730) (04c4a4ac5)

Improvements

• docs: fix broken links (3f143d2b5)
• examples: add ArgoCD GitOps example (4f0076803)
• telemetry: track the command run result and duration. More about telemetry (#3837) (a86d967ea)

0.12.53-0

chore(release): release 0.12.53-0

0.12.52

Garden 0.12.52 is out! 🎉

This release contains a deprecation notice of the built-in dashboard and introduces the new Cloud Dashboard at app.garden. The built-in dashboard will be deprecated with the next major release of Garden (0.13).

Many thanks to @jonas-jonas for their contributions 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.

• Garden v0.12.52 for Alpine AMD64 (tar.gz)
• Garden v0.12.52 for Linux AMD64 (tar.gz)
• Garden v0.12.52 for MacOS AMD64 (tar.gz)
• Garden v0.12.52 for Windows AMD64 (.zip)

Changelog

0.12.52 (2023-03-01)

Features

• cloud: Dashboard deprecation notice and garden cloud dashboard fallback (#3666) (501d5c8fc)

Bug Fixes

• cloud: continue when token refresh fails (#3814) (8d27625f0)
• example: correct entrypoint in Dockerfile in base-image example (f31b6cd9f)

0.12.52-0

chore(release): bump version to 0.12.52-0