-
-
Notifications
You must be signed in to change notification settings - Fork 146
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
Cache problem with Node.js #45
Comments
here's what we do for python: Lines 52 to 53 in ef992f5
|
Hi, I have tried to add a Would you have some hints to help me ? Below is my .github/workflows/pre-commit.yml file: And it fails with:
/home/runner/.cache/pre-commit/repon7pcj2u6/node_env-system/bin/node: line 5: /opt/hostedtoolcache/node/12.18.3/x64/bin/node: No such file or directory ESLint...................................................................Passed |
this should be fixed already in the latest version of pre-commit, what version are you running? |
Running |
then I'd recommend you try out https://pre-commit.ci instead -- it has better features anyway and github's stuff is probably un-repairably broken you also haven't shown any output so I can't know whether this is the same issue or not |
Hi everybody,
I noticed a problem with pre-commit action's cache and using Node.js environment. I'm using eslint in pre-commit and to make eslint-plugin-import work properly I need to install the dependencies. So, my workflow looks the following:
The problem is that because I only use
node-version: '14'
in the setup-node phase the Node.js version will change after a while to a newer version but the pre-commit action's cache does not care for that and tries to use a cached version where a previous version of Node.js was used and the following error occurs:and I can see that the setup-node used version 14.9.0.
I used a "workaround" a specified a fully qualified node-version but I don't think this is the best solution. Is there any way to either disable the cache or make it sensitive for the Node.js version?
Thanks!
The text was updated successfully, but these errors were encountered: