Skip to content

Conversation

@michaelbromley
Copy link
Member

This fixes a couple of issues I encountered when following Umed's instructions to create a new TypeORM release.

@michaelbromley michaelbromley merged commit 17a3c52 into typeorm:master Feb 20, 2025
33 of 34 checks passed
@coveralls
Copy link

Coverage Status

coverage: 72.364% (-0.008%) from 72.372%
when pulling 9266ebb on michaelbromley:fix-release-issues
into 9d862c8 on typeorm:master.

@alumni
Copy link
Collaborator

alumni commented Feb 20, 2025

rimraf@6 is not supported on node 18.

Adding parameters to the rimraf call should be done in other places (tests) too, there were some PRs doing that 🙂

@michaelbromley
Copy link
Member Author

Ah OK I didn't know that. Good point though - rimraf is just a dev dependency so won't affect node compatibility for end users. Or are we aiming to support node 18 also for library development?

@alumni
Copy link
Collaborator

alumni commented Feb 21, 2025

@michaelbromley we run the tests on node 18 in the pipelines (github actions). They use rimraf quite a lot, so if they didn't fail, probably it's still okay at the moment 🤷🏼‍♂️ while node 18 is no longer supported, it can happen that they didn't explicitly switch to node 20 APIs yet.

aberonni pushed a commit to global-121/typeorm that referenced this pull request Mar 5, 2025
ThbltLmr pushed a commit to ThbltLmr/typeorm that referenced this pull request Dec 2, 2025
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