Why does v1 not compute the dev env anymore?

[davdroman]

I was surprised that this is the case, as I found it quite congruent in the past for this CI action to figure out deps and install them (e.g. from tea.yml). Now everything must be made explicit via the + param, which introduces a duplication of dependency declarations if the repo already has a tea.yml for local development. Are there plans to reintroduce this functionality, or maybe implement a param like dev: true to essentially make it opt-in?

[mxcl]

There will be a separate action to do this. For now use v0 or:

- run: |
    eval "$(tea --shellcode)"
    dev
    # now do stuff since the integration is temporary

Potentially there won’t be a separate action, but I needed to get v1 out and it would be a breaking change to remove dev after v1 while it is a minor point release to add new functionality.