TC

@andrew8er, adding `dom` to my `lib` does in fact help, but that doesn't feel like the right thing to do. The challenge here is that `Blob` and other stuff from...

@FabianKramm I think you do actually call `helm dependency update` [here](https://github.com/loft-sh/devspace/blob/9689ca48f4ed62bdf030b5ef19e4962977d6d602/pkg/devspace/helm/v3/client.go#L85). I can tell cause we never call it explicitly today, and yet we're able to install helm charts that...

@FabianKramm good call, there was so much logging I didn't see the actual error up above. In this case, it just looks like a connection error. I'll see if this...

Thanks @FabianKramm . I'm on 6.0.0-beta.4 right now, which I believe is the latest published beta. Just had it happen again. It really does just look like some sort of...

fwiw, it doesn't look like `patch` or `replace` work for overriding `vars` either. ``` version: v2beta1 name: bug vars: VAR_1: 'value 1' pipelines: build: run: |- echo $VAR_1 profiles: -...

Switching the profile to use `alwaysResolve: true` also doesn't seem to help. ``` profiles: - name: asdf merge: vars: VAR_1: value: 'value 2' alwaysResolve: true ```

Variables that are ONLY defined in the profile section seem to show up correctly. So to me, this looks like the merge order got reversed from what I would expect,...

@pablorsk I gave your workaround a shot, but am not able to get it to do what I want. In our case, we have a bunch of "default" environment variables...

This likely isn't everyone's issue, but I was struggling with any `npm install` after upgrading to npm 7 or npm 8, and found that my user `.npmrc` file had `ca...

For anyone following along, it appears that this has been fixed in the most recent version of devspace: 6.2.3. I don't know when specifically it was fixed, but variables from...