fix: Use Node.js 20 in publish.yml#118

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

smockle merged 1 commit intomainfromsmockle/use-a-newer-node

Sep 16, 2024

Merged

fix: Use Node.js 20 in publish.yml#118

smockle merged 1 commit intomainfromsmockle/use-a-newer-node

Sep 16, 2024

Conversation

Copy link

Contributor

smockle commentedSep 16, 2024

Node.js 16 has been end-of-life’d for more than a year. This PR updates the publish workflow to use Node.js 20, the Active LTS, instead.

#117 updated a package so thatstructuredClone is now called. That API did not exist in Node.js 16, so updating to a newer version avoids workflow failures.

fix: Use Node.js 20 in publish.yml

4af9baf

Node.js 16 has been end-of-life’d for more than a year. This PR updates the publish workflow to use Node.js 20, the Active LTS, instead.#117 updated a package so that `structuredClone` is now called. That API did not exist in Node.js 16, so updating to a newer version avoids workflow failures.