Skip to content

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

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
Sep 16, 2024
Merged

Conversation

smockle
Copy link
Contributor

@smockle smockle commented Sep 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 that structuredClone is now called. That API did not exist in Node.js 16, so updating to a newer version avoids workflow failures.

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.
@smockle smockle requested a review from a team as a code owner September 16, 2024 17:31
@smockle smockle merged commit a1959e8 into main Sep 16, 2024
4 of 5 checks passed
@smockle smockle deleted the smockle/use-a-newer-node branch September 16, 2024 23:53
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants