Skip to content
This repository has been archived by the owner on Dec 19, 2024. It is now read-only.

Hot Fix: Make Runners Explicitly use Node Version 16 #1381

Merged
merged 1 commit into from
Feb 18, 2023

Conversation

ardelato
Copy link
Contributor

Description

The default node version for the runners was changed to 18, which is not compatible with our current setup. Unfortunately, this change was only tracked as an issue and was not announced on GitHub's blog (https://github.blog/changelog/label/actions/), which is why we did not notice it.

In order to fix this, we need to explicitly set the node version to 16 for all our workflows that use node/pnpm.

QA Notes:

qa_req 0 CI should pass

References:
actions/runner-images#7002
https://ifixit.slack.com/archives/C02SMF0AZPF/p1676677777249139

The default node version for the runners was changed to 18, which
is not compatible with our current setup. Unfortunately, this change
was not properly announced, which is why we did not notice it. There is
only a GH issue about it at the moment.
actions/runner-images#7002

In order to fix this, we need to explicitly set the node version to 16
for all our workflows that use node/pnpm.
@vercel
Copy link

vercel bot commented Feb 18, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated
react-commerce ✅ Ready (Inspect) Visit Preview 💬 Add your feedback Feb 18, 2023 at 0:32AM (UTC)
react-commerce-prod ✅ Ready (Inspect) Visit Preview 💬 Add your feedback Feb 18, 2023 at 0:32AM (UTC)

Copy link
Member

@mlahargou mlahargou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CR 📱

Thanks for hoping on this!

@github-actions
Copy link
Contributor

📦 Next.js Bundle Analysis

This analysis was generated by the next.js bundle analysis action 🤖

This PR introduced no changes to the javascript bundle 🙌

@danielbeardsley
Copy link
Member

Some of our tests are failing because part of the next-js install process downloads a binary from sharp (an image processing module) and that service only payed for so much egress data:

sharp: Installation error: Status 503 Egress is over the account limit.

At least that's how it seems.

That isn't the fault of this pull, though it'd be nice to depend on them less so we aren't downloading very much or anything during CI.

CR 👍

@ardelato ardelato merged commit 39a877a into main Feb 18, 2023
@ardelato ardelato deleted the hot-fix--make-runners-use-node-16 branch February 18, 2023 00:45
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants