Skip to content
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: bump workflow node version to 20 #4034

Merged
merged 2 commits into from
Jan 9, 2025

Conversation

rix0rrr
Copy link
Contributor

@rix0rrr rix0rrr commented Jan 9, 2025

lru-cache has dropped support for Node 18, and now requires Node 20 or higher.

When projen creates new projects that use jest, it pulls in lru-cache using the following dependency path:

jest > @jest/core > @jest/transform > @babel/core > @babel/helper-compilation-targets > lru-cache

That happens to install the newest lru-cache version, which no longer works on Node 18, and so our tests fail.

Bump our workflow Node to 20 to at least make our PR build pass again (should we use lts/* to be done with this periodic breakage?)

This means that projen new typescript-app will no longer work on Node 18.

I don't know if this should have bearing on projen's minimum Node version; I suppose technically not, and people with a working package-lock will be unaffected... but it might be hard to explain the intricacies to users.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

`lru-cache` has dropped support for Node 18, and now requires Node 20 or
higher.

When `projen` creates new projects that use jest, those pull in
`lru-cache` using the following dependency path:

```
jest > @jest/core > @jest/transform > @babel/core > @babel/helper-compilation-targets > lru-cache
```

That happens to install the newest `lru-cache` version, which no longer
works on Node 18, and so our tests fail.

Bump our workflow Node to 20 to at least make our PR build pass again.

I don't know if this should have bearing on projen's minimum node
version; I suppose *technically* not, and people with a working
`package-lock` will be unaffected... but it might be hard to explain the
intricacies to users.
@cdklabs-automation cdklabs-automation added this pull request to the merge queue Jan 9, 2025
Merged via the queue into main with commit c275f5f Jan 9, 2025
15 checks passed
@cdklabs-automation cdklabs-automation deleted the huijbers/node-version branch January 9, 2025 10:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants