-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
Cannot build Astro site with Node 20, "actions/checkout@v4" and "withastro/action@v2" #45
Comments
I just tried renaming my |
I've managed to get node 18 working again by explicitly adding a node step: I also reverted the other steps back to their original values. |
Your workflow file is currently using actions that are not at the latest versions, I think that might be the cause Can you try bumping versions, comment out your Here are the version bumps you can try:
|
I think your lock file has to be Would be nice if |
Applying suggestions from withastro/action#45 (comment)
fyi, was having the same problem on my end with
Specifying |
You're right! pipefail is on: set -o pipefail
INPUT_PM=pnpm
echo "$INPUT_PM" | grep -o '@.*' | sed 's/^@//'
echo $? this will show 1, which means command has failed. pipefail is off: set +o pipefail
INPUT_PM=pnpm
echo "$INPUT_PM" | grep -o '@.*' | sed 's/^@//'
echo $? this will show 0, which means command has not failed. So to resolve the issue we have 2 possibilities:
I've created a PR for the solution number 1 |
I bumped my Astro website Node version to 20 earlier today, but discovered I could no longer build and deploy via Github pages.
There's a related Node 20 bug, which is now closed.
And the related PR has been merged.
So... I have just modified my Github pages workflow YML with latest versions:
https://github.com/basher/basher-website/blob/master/.github/workflows/static.yml
But... I'm still getting build errors. The error doesn't provide me with any useful info:
https://github.com/basher/basher-website/actions/runs/7974519592/job/21770594265#step:3:41
Any ideas??? 🤔
The text was updated successfully, but these errors were encountered: