Then don't use the GitHub Actions defaults? Write your own Nodejs install script and use that instead.
That's what I do and it's pretty stable: https://github.com/alshdavid-templates/siteforge/blob/main/....
That's what I do and it's pretty stable: https://github.com/alshdavid-templates/siteforge/blob/main/....
Couple more thoughts and unsolicited feedback from a quick eyeball:
- Use https://
- Wrap everything in a shell function to ensure that partial content is not executed.
- Wrap variable substitutions with "${OUTPUT_DIR}" to prevent arg splitting if they contain whitespace. Line 124, `rm -rf $OUT_DIR_INSTALL` is pretty scary if invoked with whitespace in OUT_DIR.
- Download nodejs tarball to temp directory and then extract them to prevent partial extraction
echo "export FOO=bar" | bash
echo $FOO
I am trying to set the variables in the current shell eval $(echo "echo 'export FOO=bar'" | bash)
echo $FOO
So my script writes variables to stdout and redirects everything else to stderr. I use this to update a `.bashrc` while also updating the current shell uses: actions/checkout@v4
That uses the Node that is provided by GitHub, and that will break in the future.