Repository navigation
Updating actions/cache@v3 to v4 to run on node20 #14
Description
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
actions/cache@v3 runs on node16 which is deprecated, requesting to migrate to v4
Activity
kishaningithub commentedon Aug 7, 2024
@devlsat This action is a shell action and fundamentally does not use node js. However, note that Amazon linux 2 has problems running node 20 because of its dependency with old GLIBC version.
If you are facing issues in running, kindly consider this option
setup-python-amazon-linux/.github/workflows/test.yml
Line 10 in 976096e
devlsat commentedon Aug 7, 2024
Okay thanks for the update
So, doing #15 this won't help?
Since
kishaningithub commentedon Aug 7, 2024
You are right.. this might help..
Looking into why the CI did not get triggered for your PR.
devlsat commentedon Aug 13, 2024
Closing the issue
kishaningithub commentedon Aug 18, 2024
Reopening this issue to keep track of making this action node version agnostic
kishaningithub commentedon Aug 27, 2024
@devlsat This Concern of referencing old node version is now fixed with the latest release. If you run trigger a new job you should see it disappear. As a big performance bonus, the python installation time should go from ~1 minute to ~25 seconds .
Give it a spin and let know your feedback :-)
devlsat commentedon Aug 28, 2024
Facing this issue with the latest version
Was working fine with v1.0.8
kishaningithub commentedon Aug 28, 2024
@devlsat Interestingly v1.0.8 also has references to the $HOME variable.. Thinking about potential root causes... you have any thoughts?
setup-python-amazon-linux/action.yml
Line 33 in 976096e
kishaningithub commentedon Aug 28, 2024
@devlsat Have released a possible fix for this in the latest release (v1.0.12).. Can you try running it with either v1.0.12 tag or v1 tag?
devlsat commentedon Aug 29, 2024
Nope
Same error, but got a description this time
kishaningithub commentedon Aug 29, 2024
@devlsat If you login to the self hosted runner and run
echo "$HOME"does it fail or succeed?devlsat commentedon Sep 2, 2024
Blank empty output
kishaningithub commentedon Sep 2, 2024
@devlsat Is this action directly running in the EC2 runner machine or within a Docker container runner?
1 remaining item
kishaningithub commentedon Sep 2, 2024
I launched an EC2 with amazon linux 2023 AMI and i see
$HOMEis present (screenshot below).What is the output of
whoamicommand? Also is the container being started in a login shell if not this problem might occurkishaningithub commentedon Sep 2, 2024
@devlsat I have released a possible fix for this in the latest v1.0.13 version viz to force a login shell for bash execution. Can you try upgrading to v1.0.13 or trigger a new run with v1 version?
devlsat commentedon Sep 3, 2024
It doesnt
kishaningithub commentedon Sep 6, 2024
@devlsat Which is the version of this action that is working fine for you?
devlsat commentedon Sep 6, 2024
v1.0.8 works perfectly
kishaningithub commentedon Nov 11, 2024
@devlsat Have released a new version v1.0.14 which i think should fix the above issue. Kindly check and let me know.
kishaningithub commentedon Dec 25, 2024
@devlsat Is it correct to assume the new versions of this action are working for you?
ivanokhotnikov commentedon Jun 4, 2025
@kishaningithub I've tried v1.0.14 and v1.0.15, these didn't work for me, I was getting same error as @devlsat had.
v1.0.8 works ok for me though.
kishaningithub commentedon Jun 4, 2025
@ivanokhotnikov Can you give a screenshot or a text version of the full error you are getting? That will help me debug better
ivanokhotnikov commentedon Jun 4, 2025
kishaningithub commentedon Jun 4, 2025
@ivanokhotnikov Have published a new version v1.0.16 with the fix. Can you give it a spin? You can either use v1 or v1.0.16
ivanokhotnikov commentedon Jun 4, 2025
same issue, I'm not sure if caching is at play here, but I won't be able to investigate further
kishaningithub commentedon Jun 4, 2025
Thanks for the screenshot @ivanokhotnikov It was useful! Have released a new version v1.0.17 with the fix. Can you give it a spin? You can either use v1 or v1.0.17
kishaningithub commentedon Jun 13, 2025
@ivanokhotnikov Did you get a chance to try out the latest version?