Unexpected input 'env_vars'

[leezu]

      - name: Upload coverage to Codecov
        uses: codecov/codecov-action@v1
        with:
          env_vars: OS,PYTHON

triggers warning Unexpected input 'env_vars', valid inputs are ['name', 'token', 'file', 'flags', 'fail_ci_if_error'] despite following the example of https://github.com/codecov/codecov-action#arguments

[TsumiNa]

have same warning

[thuitaw]

Got the same error here

##[warning]Unexpected input 'env_vars', valid inputs are ['name', 'token', 'file', 'flags', 'fail_ci_if_error']
Run codecov/codecov-action@v1
  with:
    token: ***
    file: ./coverage.xml
    flags: unittests
    env_vars: OS,PYTHON
    name: codecov-umbrella
    fail_ci_if_error: true
  env:
    pythonLocation: /opt/hostedtoolcache/Python/3.6.10/x64
bash codecov.sh -f ./coverage.xml -n codecov-umbrella -F unittests -Z

[pmeier]

env_vars was only introduced by v0.1.7. You could pin the version in the workflow:

- name: Upload coverage to Codecov
  uses: codecov/codecov-action@v1.0.7
  with:
    env_vars: OS,PYTHON

[sjjessop]

How about updating the readme so that the example with env_vars in it uses v1.0.7 (or whatever is needed to support all the options in the example)?

I guess the problem there is you'll end up wanting to keep updating the readme to the latest, but it would be helpful to new users for that example to work verbatim.

[thomasrockhu]

We have updated the v1 tag to the latest, apologies for this.

[vivodi]

What is the purpose of env_vars? Can it be viewed through Codecov's UI? Why do I feel that setting it makes no difference?