Error activating dev with action.yml present

[gaggle]

I get an error with dev when entering my project.

The context:

$ tea --version
tea 1.0.0-alpha.3

$ cat elixir_script/.tea.yaml
dependencies:
  elixir-lang.org: =1.15.4
  erlang.org: =26.0.2

$ cat elixir_script/action.yml
name: Elixir Script
author: Jon Lauridsen
description: Run simple Elixir scripts
branding:
  color: orange
  icon: code
inputs:
  script:
    description: The script to run
    required: true
  debug:
    description: Whether to tell the GitHub client to log details of its requests. true or false. Default is to run in debug mode when the GitHub Actions step debug logging is turned on.
    default: ${{ runner.debug == '1' }}
outputs:
  result:
    description: The stringified return value of the script
runs:
  using: docker
  image: Dockerfile

And dev errors when entering the folder:

$ cd elixir_script/
× unexpected error object null is not iterable (cannot read property Symbol(Symbol.iterator))
│ TypeError: object null is not iterable (cannot read property Symbol(Symbol.iterator))
│     at github_actions (file:///Users/runner/work/cli/cli/src/utils/devenv.ts:191:19)
│     at eventLoopTick (ext:core/01_core.js:183:11)
│     at async default (file:///Users/runner/work/cli/cli/src/utils/devenv.ts:39:11)
│     at async default (file:///Users/runner/work/cli/cli/src/modes/internal.activate.ts:16:34)
│     at async default (file:///Users/runner/work/cli/cli/src/app.ts:69:35)
│     at async file:///Users/runner/work/cli/cli/entrypoint.ts:68:3
╰─➤ https://github.com/teaxyz/cli/issues/new

This error is caused by the presence of the action.yml file, if I delete it then dev works:

$ cd ..
$ rm elixir_script/action.yml
$ cd elixir_script/
tea +erlang.org=26.0.2 +elixir-lang.org=1.15.4 +git-scm.org

[gaggle]

Is this a variant of the fix applied in ed51fe7? I can't quite make sense of devenv.ts:191:19 since 191 is a call to Deno.open, but the error also says github_actions which is the function that parses the action.yml file 🤔

[mxcl]

Will fix in alpha.4. apologies. I thought I'd handled all these sorts of cases finally.