Closed wpbonelli closed 7 months ago
I want to keep downloadTool
as changing this to for example the install.sh script can break things in corporate environments behind a proxy (I had this problem in https://github.com/mamba-org/setup-micromamba/pull/61 before).
Not sure about PIXI_VERSION
as this introduces a second way to basically do the same thing without being clear which the preferred way is. I'm also unsure how other setup-*
actions do this. I would suppose they also only use the GitHub-provided input arguments.
It does look like other setup-*
actions just use the input. I will close this.
The pixi docs describe several environment variables which control the behavior of the installer scripts. I know this action installs pixi via
downloadTool()
, not with the install scripts, but perhaps still worth supporting? At least the ones shared on all platforms:PIXI_VERSION
(this is justVERSION
on linux/mac, maybe worth standardizing?)PIXI_HOME
Just convenience, but it would be nice to be able to set
PIXI_VERSION
at the top of a workflow instead of settingversion
separately wherever this action is used.I guess the way to do this would be to check
process.env
here