-
Notifications
You must be signed in to change notification settings - Fork 8
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
chore: update CI action versions #186
Conversation
And link Node’s version to the one in repo
@mxdvl Thanks for your PR! Currently the CI is failing on all kinds of Prettier warnings. Are these a side effect of your changes? |
It must be, somehow, but I'm not sure why… Does the vue lint command work locally on your machine with Node 16.17? |
|
I'm okay with the changes Prettier suggests. As long as the codebase is consistent. Can we let Prettier just fix them? |
Also I wonder if this PR will run into the same ssh/https trouble as seen here: https://github.com/Wakamai-Fondue/wakamai-fondue-site/actions/runs/11230829820/job/31218950314?pr=185 I'm trying to fix that here: #187 The problem is apparently that we used to load the Engine dependency over ssh while developing it before making everything public. Since the repo is public now we can just load it over https instead of ssh. My commit there seems to fix that particular error, now stranding on another. Oh well, diving into that one now! |
$ npx --write .
Thanks both, have done so in 4a95abd, but the linter wanted something slightly different, so you can find the result of |
$ npm run lint
@mxdvl I get the error
Is that something that you added but didn't commit? |
Oh I just noticed Wakamai-Fondue/wakamai-fondue-engine#66 which might be relevant? |
Oh no I thought I'd reverted that — fix incoming. It was only a way of ensuring we could run the exact same check locally as in CI, but it'll extract it to its own PR. |
This is another approach that we could go with, using a matrix of Node versions, but I think that having a consistent version locally and on CI is a simpler first step.
Done ✅ |
There were two options on how to handle this. The chosen one pleases the linter. Signed-off-by: André Jaenisch <[email protected]>
Thanks, @mxdvl ! |
And link Node’s version to the one in repo