New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The add-path
command and set-env
command is disabled
#101
Comments
See #99. |
Agh, sorry, thought I was ahead of the curve here. Appreciate you guys addressing it so fast! |
Oh, sure, nice idea. There might be more reports coming. Shall we also pin it for a week or so? |
@bradyrx Can you add a little comment on your opening message stating the solution for visibility? |
Dark GitHub feels wrong 😄 |
Done, thanks guys! Easy fix and quick communication. |
Updated `goanpeca/setup-miniconda@v1` hook to `conda-incubator/setup-miniconda@v2` because of the `add-path` command and `set-env` command is disabled - see conda-incubator/setup-miniconda#101
cheers, guys! will buy pints if this works well for us too 🍺 |
it works very well with the new hooks - much appreciated, folks here! 🍺 |
See conda-incubator/setup-miniconda#101 Signed-off-by: julian <julian.burellaperez@heig-vd.ch>
Closing this one, I think we should be fine moving forward :) |
SOLUTION: Simply update your
goanpeca/setup-miniconda@v1
hook toconda-incubator/setup-miniconda@v2
and the error should go away.It looks like something changed to Github Actions today, as our
setup-miniconda
hook is breaking with the following error:See our error in more detail here.
And the workflow code here.
I found that this is affecting other hooks, so I imagine it must be a Github Actions change. E.g., camerahub/camerahub#630, apache/tvm#6925.
EDIT: Actually it looks like GA announced this back in October, but went into effect today.
The text was updated successfully, but these errors were encountered: