Skip to content

Conversation

@n-older
Copy link
Contributor

@n-older n-older commented Jan 14, 2025

This also simultaneously upgrades cross-spawn to a secure version since eslint depends on it.

- Simultaneously upgrades cross-spawn to a secure version
@n-older n-older requested a review from jclusso January 14, 2025 15:00
@jclusso
Copy link
Member

jclusso commented Jan 14, 2025

@n-older what do we do regarding the CI failing now for Node 14 and 16? Or should we just drop support for those in the CI?

@n-older
Copy link
Contributor Author

n-older commented Jan 14, 2025

@n-older what do we do regarding the CI failing now for Node 14 and 16? Or should we just drop support for those in the CI?

Hmm I didn't know about these tests beforehand. I mean it's just a dev dependency so maybe we just axe these older version tests.

@jclusso
Copy link
Member

jclusso commented Jan 14, 2025

@n-older I think we can cause 14 and 16 are so old anyway. Remove them from the actions config in this PR and that'll solve it.

@n-older
Copy link
Contributor Author

n-older commented Jan 14, 2025

Did I do that correctly? Not sure why they're still showing for me unless it's some weird GitHub bug.
CleanShot 2025-01-14 at 10 21 25

@jclusso jclusso merged commit 8648e8e into master Jan 14, 2025
3 checks passed
@jclusso jclusso deleted the upgrade-eslint branch January 14, 2025 23:33
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