chore(release): bump version to v0.11.0

CHANGELOG.md

@@ -1,4 +1,113 @@
 
+<a name="v0.11.0"></a>
+## [v0.11.0](https://github.com/garden-io/garden/compare/v0.10.16...v0.11.0) (2020-01-13)
+
+### Bug Fixes
+
+* failing init if remote is not set ([938bb200](https://github.com/garden-io/garden/commit/938bb200))
+* force anlytics events queue flush ([89ea096c](https://github.com/garden-io/garden/commit/89ea096c))
+* occasional unhelpful error messages when shelling out ([92849a01](https://github.com/garden-io/garden/commit/92849a01))
+* remove resources only when tiller not deployed ([b2b30b17](https://github.com/garden-io/garden/commit/b2b30b17))
+* **build:** ensure that exec modules are rebuilt on when garden is run ([4d2cccea](https://github.com/garden-io/garden/commit/4d2cccea))
+* **build:** validate helm modules at build rather than configure phase ([7551646a](https://github.com/garden-io/garden/commit/7551646a))
+* **cli:** enable running 'config analytics-enabled' with no project ([cc151a3a](https://github.com/garden-io/garden/commit/cc151a3a))
+* **cli:** ensure 'noProject' commands run in invalid projects ([4e7ff830](https://github.com/garden-io/garden/commit/4e7ff830))
+* **config:** detect overlap after resolving module configs ([3fd520e9](https://github.com/garden-io/garden/commit/3fd520e9))
+* **config:** do not set default include if exclude is set + add tests ([5f7dd186](https://github.com/garden-io/garden/commit/5f7dd186))
+* **core:** use fresh statuses in get status cmd ([b0ebf22f](https://github.com/garden-io/garden/commit/b0ebf22f))
+* **core:** fix empty runtimeContext check ([0b2eae5e](https://github.com/garden-io/garden/commit/0b2eae5e))
+* **core:** error when attempting to forward to restricted local port ([e6a103bf](https://github.com/garden-io/garden/commit/e6a103bf))
+* **core:** extraneous build step in stack graph when no build is needed ([f452c00e](https://github.com/garden-io/garden/commit/f452c00e))
+* **core:** ensure builds are staged when module has no build handler ([c4c13d23](https://github.com/garden-io/garden/commit/c4c13d23))
+* **dashboard:** hide ingress view when showing task/test results ([6879bf1c](https://github.com/garden-io/garden/commit/6879bf1c))
+* **docs:** fix dashboard README ([5152dded](https://github.com/garden-io/garden/commit/5152dded))
+* **k8s:** use configured ingress ports when installing nginx ([919e4f35](https://github.com/garden-io/garden/commit/919e4f35))
+* **k8s:** only cleanup generated namespaces ([c94b2ca8](https://github.com/garden-io/garden/commit/c94b2ca8))
+* **k8s:** fix issues with helm 2to3 migration ([4b3629bf](https://github.com/garden-io/garden/commit/4b3629bf))
+* **k8s:** helm migration issue with non-deployed releases ([d97adf78](https://github.com/garden-io/garden/commit/d97adf78))
+* **k8s:** timeout error in cleanup-cluster-registry script ([b5451e3b](https://github.com/garden-io/garden/commit/b5451e3b))
+* **k8s:** in-cluster registry updates would hang with RWO volumes ([fd264141](https://github.com/garden-io/garden/commit/fd264141))
+* **k8s:** ensure Garden can upgrade garden-nginx release ([b244c8e0](https://github.com/garden-io/garden/commit/b244c8e0))
+* **k8s:** play nice with Helm 2 (Tiller) when users still need it ([8f803c3c](https://github.com/garden-io/garden/commit/8f803c3c))
+* **k8s:** ensure helm migration works on Windows ([2771a982](https://github.com/garden-io/garden/commit/2771a982))
+* **k8s:** don't throw init error if garden-system services are modified ([0aff683e](https://github.com/garden-io/garden/commit/0aff683e))
+* **k8s:** uninstall-garden-services command now works more reliably ([a9671543](https://github.com/garden-io/garden/commit/a9671543))
+* **k8s:** error when running cluster-init command ([dd94e05b](https://github.com/garden-io/garden/commit/dd94e05b))
+* **k8s:** default to NFS for in-cluster builder storage for local k8s ([10b90e14](https://github.com/garden-io/garden/commit/10b90e14))
+* **k8s:** make sure Helm 3 migration is run for project namespaces ([70403730](https://github.com/garden-io/garden/commit/70403730))
+* **openfaas:** fix issue in deployment retry handler ([f6e2cf3a](https://github.com/garden-io/garden/commit/f6e2cf3a))
+* **vcs:** ensure module versions are stable between runtimes ([3b438a4e](https://github.com/garden-io/garden/commit/3b438a4e))
+* **watcher:** fix segfault on Mac when reloading config ([265696e9](https://github.com/garden-io/garden/commit/265696e9))
+
+### Code Refactoring
+
+* **core:** allow plugins to augment the module graph ([b2509e9c](https://github.com/garden-io/garden/commit/b2509e9c))
+* **k8s:** avoid building Helm chart before getting deploy status ([aa06e8e3](https://github.com/garden-io/garden/commit/aa06e8e3))
+
+### Features
+
+* add a migration command for migrating from v0.10 to v0.11 ([765b324e](https://github.com/garden-io/garden/commit/765b324e))
+* hadolint provider ([715abe06](https://github.com/garden-io/garden/commit/715abe06))
+* **core:** use service's port when forwarding to localhost if available ([26bbeca3](https://github.com/garden-io/garden/commit/26bbeca3))
+* **k8s:** add support for KinD ([87a69787](https://github.com/garden-io/garden/commit/87a69787))
+* **providers:** add conftest providers ([da24e775](https://github.com/garden-io/garden/commit/da24e775))
+
+### Improvement
+
+* set default include on Helm modules ([fca600dd](https://github.com/garden-io/garden/commit/fca600dd))
+* **analytics:** improve the data collection ([#1438](https://github.com/garden-io/garden/issues/1438)) ([04ffbbe6](https://github.com/garden-io/garden/commit/04ffbbe6))
+* **cli:** remove `garden init` command ([3f9da06c](https://github.com/garden-io/garden/commit/3f9da06c))
+* **container:** automatically set include field based on config ([7cef10eb](https://github.com/garden-io/garden/commit/7cef10eb))
+* **core:** update to get-port with restricted port fix ([ca0992bb](https://github.com/garden-io/garden/commit/ca0992bb))
+* **core:** allow relative symlinks within module root for builds ([f7449e17](https://github.com/garden-io/garden/commit/f7449e17))
+* **hadolint:** log one-line warning message when applicable ([08b86968](https://github.com/garden-io/garden/commit/08b86968))
+* **hadolint:** gracefully handle conflicting modules and names ([600bedfb](https://github.com/garden-io/garden/commit/600bedfb))
+* **k8s:** set --atomic flag on helm upgrade ([7a9ed310](https://github.com/garden-io/garden/commit/7a9ed310))
+* **k8s:** update bundled nginx controller version ([40729a46](https://github.com/garden-io/garden/commit/40729a46))
+* **k8s:** switch to Helm 3 and remove Tiller ([a6940e0a](https://github.com/garden-io/garden/commit/a6940e0a))
+* **k8s:** auto-set include field on kubernetes module type ([03033ba4](https://github.com/garden-io/garden/commit/03033ba4))
+* **k8s:** stop bundling kubernetes-dashboard in garden-system ([e3d32e27](https://github.com/garden-io/garden/commit/e3d32e27))
+
+### BREAKING CHANGE
+
+
+If not set by the user, the `include` field on Helm modules now defaults to:
+
+```javascript
+["*", "charts/**/*", "templates/**/*"]
+```
+
+if the module has local chart sources, otherwise to:
+
+```javascript
+["*", "charts/**/*", "templates/**/*"]
+```
+
+Previously, Helm modules would simply include all content under the
+module path.
+
+If your Helm modules doesn't have `include` set and depends
+on content that's not captured with the default include, you will need
+to update the relevant `garden.yml` file and set the includes manually.
+
+Helm 2.x is no longer supported. The migration (both for garden-system
+services and your project namespace) is handled automatically
+via the `helm 2to3` plugin. It is _possible_ that the automatic
+migration fails though (due to any number of potential issues with
+Helm or issues exposed with individual charts upon upgrade).
+
+We've tried to cover and test for these  cases as best we can, but can't
+rule out issues, so you may need to intervene (by e.g. manually removing
+resources or using the helm CLI directly) if migration or upgrades after
+deployment throw errors.
+
+If you do run into tricky issues, please don't hesitate to log issues
+on GitHub or ping us on Slack and we'll be happy to help.
+
+Any user scripts that run `garden init` will need to be updated to
+remove those references.
+
+
 <a name="v0.10.16"></a>
 ## [v0.10.16](https://github.com/garden-io/garden/compare/v0.10.15...v0.10.16) (2019-12-06)
 

README.md

@@ -19,7 +19,7 @@
 - **Shared development clusters with fast in-cluster building and image caching for Kubernetes.** This allows teams to easily share build and test results, and for CI to become much faster because it can use the same build and test caches as the team.
 - Get helpful information when your deployments fail. Garden collects events and logs and displays them prominently when issues come up, and strives to "fail fast", so that you don't need to wait for timeouts or dive into kubectl whenever something is wrong.
 - Easily write [integration test suites](https://docs.garden.io/guides/development-workflows#tests-and-dependencies) that have runtime dependencies. Run tests *before* pushing your code to CI, and avoid having to mock or stub your own services.
-- Define [tasks](https://github.com/garden-io/garden/tree/v0.10.16/examples/tasks) that run as part of your deployment process—e.g. database migrations or scaffolding.
+- Define [tasks](https://github.com/garden-io/garden/tree/v0.11.0/examples/tasks) that run as part of your deployment process—e.g. database migrations or scaffolding.
 - [Hot reload](https://docs.garden.io/guides/hot-reload) lets you near-instantaneously update code and static files in containers as they run, for services that support in-place reloading.
 - [Remote sources](https://docs.garden.io/guides/using-remote-sources) support allows your project to automatically pull code from different repositories.
 - The built-in web **dashboard** gives you a full overview of your stack (and many more UI features are planned to further aid with development).
@@ -51,7 +51,7 @@
 
 ## Quick start
 
-With the CLI installed, you can try out a few commands using the [Demo Project](https://docs.garden.io/examples/demo-project) from our [example projects](https://github.com/garden-io/garden/tree/v0.10.16/examples). The example project consists of a couple of simple modules, each defining one service.
+With the CLI installed, you can try out a few commands using the [Demo Project](https://docs.garden.io/examples/demo-project) from our [example projects](https://github.com/garden-io/garden/tree/v0.11.0/examples). The example project consists of a couple of simple modules, each defining one service.
 
 *Note: This example assumes you have a local Kubernetes instance running.*
 
@@ -96,11 +96,11 @@ Overview:
 
 - [Using Garden](https://docs.garden.io/using-garden)—short Guides on incrementally adding the main Garden constructs to your project.
 - [Guides](https://docs.garden.io/guides)—development workflows, Garden configuration files, usage with remote Kubernetes clusters, and setting up hot reload.
-- [Example Projects](https://docs.garden.io/examples)—guides based on some of the [examples](https://github.com/garden-io/garden/tree/v0.10.16/examples).
+- [Example Projects](https://docs.garden.io/examples)—guides based on some of the [examples](https://github.com/garden-io/garden/tree/v0.11.0/examples).
 - [Reference](https://docs.garden.io/reference)—glossary, commands reference, configuration files reference, and template strings reference.
 - [FAQs](https://docs.garden.io/#faqs).
 
-The [examples](https://github.com/garden-io/garden/tree/v0.10.16/examples) folder of our repository also shows a myriad of different ways to use Garden. Check out the README in each example for more information
+The [examples](https://github.com/garden-io/garden/tree/v0.11.0/examples) folder of our repository also shows a myriad of different ways to use Garden. Check out the README in each example for more information
 
 ## How does it work?
 

dashboard/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dashboard",
-  "version": "0.1.16",
+  "version": "0.2.0",
   "private": true,
   "devDependencies": {
     "@types/d3": "^5.7.2",
@@ -35,7 +35,7 @@
     "emotion": "^10.0.9",
     "flexboxgrid": "^6.3.1",
     "flexboxgrid-helpers": "^1.1.3",
-    "garden-service": "^0.10.16",
+    "garden-service": "^0.11.0",
     "http-proxy-middleware": "^0.19.1",
     "immer": "^3.1.3",
     "lodash": "^4.17.11",

docs/examples/README.md

@@ -18,5 +18,5 @@ This is an example project of how to set up TLS using the `mkcert` tool.
 
 ## Other example projects
 
-You can also go straight to the [examples](https://github.com/garden-io/garden/tree/v0.10.16/examples) directory in the
+You can also go straight to the [examples](https://github.com/garden-io/garden/tree/v0.11.0/examples) directory in the
 Garden repository, to look at a variety of fully defined example projects.

docs/examples/demo-project.md

@@ -17,7 +17,7 @@ This tutorial assumes that you already have a running [installation of Garden](.
 
 ## Clone the example repo
 
-The code for this tutorial can be found in our Github repository under the [examples directory](https://github.com/garden-io/garden/tree/v0.10.16/examples). We'll use the [demo-project-start](https://github.com/garden-io/garden/tree/v0.10.16/examples/demo-project-start/) example and work our way from there. The final version is under [demo-project](https://github.com/garden-io/garden/tree/v0.10.16/examples/demo-project).
+The code for this tutorial can be found in our Github repository under the [examples directory](https://github.com/garden-io/garden/tree/v0.11.0/examples). We'll use the [demo-project-start](https://github.com/garden-io/garden/tree/v0.11.0/examples/demo-project-start/) example and work our way from there. The final version is under [demo-project](https://github.com/garden-io/garden/tree/v0.11.0/examples/demo-project).
 
 First, let's clone the examples repo, change into the directory, and take a look inside:
 

docs/examples/tls-project.md

@@ -8,7 +8,7 @@ This project shows how you can configure a TLS certificate to use for local deve
 For the example to work you need to configure a local certificate authority (CA) on your computer for development. We'll use
 [mkcert](https://github.com/FiloSottile/mkcert) for this purpose.
 
-_Note: The source code for this project can be found at: [https://github.com/garden-io/garden/tree/v0.10.16/examples/local-tls](https://github.com/garden-io/garden/tree/v0.10.16/examples/local-tls)._
+_Note: The source code for this project can be found at: [https://github.com/garden-io/garden/tree/v0.11.0/examples/local-tls](https://github.com/garden-io/garden/tree/v0.11.0/examples/local-tls)._
 
 ## Setup
 

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

@@ -23,7 +23,7 @@ The guide is based on the [Remote Kubernetes](https://docs.garden.io/guides/remo
 
 ## Project overview
 
-The project is based on our basic [demo-project](https://github.com/garden-io/garden/tree/v0.10.16/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/v0.11.0/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 in 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 `master` branch.
 

docs/guides/container-modules.md

@@ -57,7 +57,7 @@ If you specify a tag as well, for example `image: my-org/my-container:v1.2.3`, t
 
 In the case of Kubernetes, 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/v0.10.16/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/v0.11.0/examples/demo-project):
 
 ```yaml
 kind: Module
@@ -141,7 +141,7 @@ 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 offical [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/v0.10.16/examples/kubernetes-secrets) for a working example.
+Also check out the [Kubernetes Secrets example project](https://github.com/garden-io/garden/tree/v0.11.0/examples/kubernetes-secrets) for a working example.
 
 ## Running tests
 

docs/guides/remote-kubernetes.md

@@ -124,7 +124,7 @@ to your registry's documentation on how to do that (for Docker Hub you simply ru
 
 ### 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 examples for [using Garden with Ambassador](https://github.com/garden-io/garden/tree/v0.10.16/examples/ambassador) and [with Istio](https://github.com/garden-io/garden/tree/v0.10.16/examples/istio) in our [examples directory](https://github.com/garden-io/garden/tree/v0.10.16/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 examples for [using Garden with Ambassador](https://github.com/garden-io/garden/tree/v0.11.0/examples/ambassador) and [with Istio](https://github.com/garden-io/garden/tree/v0.11.0/examples/istio) in our [examples directory](https://github.com/garden-io/garden/tree/v0.11.0/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.