Skip to content

Conversation

MichaelDeBoey
Copy link
Member

No description provided.

@MichaelDeBoey MichaelDeBoey requested review from a team, MatanBobi, gnapse and timdeschryver August 5, 2025 10:16
@MatanBobi
Copy link
Member

Thanks @MichaelDeBoey!
I think we can also safely remove node 14 and node 16 (for tests at least). Thoughts?

@MichaelDeBoey
Copy link
Member Author

@MatanBobi I don't think we should remove those if we're not actually dropping support for them

@MichaelDeBoey MichaelDeBoey enabled auto-merge (squash) August 5, 2025 12:02
@MichaelDeBoey MichaelDeBoey force-pushed the add-tests-for-node-22-24 branch from beb35af to c85ac99 Compare August 5, 2025 12:02
@MichaelDeBoey MichaelDeBoey merged commit fafd8ca into main Aug 5, 2025
7 checks passed
@MichaelDeBoey MichaelDeBoey deleted the add-tests-for-node-22-24 branch August 5, 2025 12:03
@MatanBobi
Copy link
Member

@MatanBobi I don't think we should remove those if we're not actually dropping support for them

I understand this approach and I honestly don't have a strong opinion on that. But I just wanted to mention that probably if I were to see a bug happening in a new feature only for Node 14 and Node 16 right now, I would not invest time on fixing them so I also think that we shouldn't test for that, but as I said, no strong opinion :)

Copy link

🎉 This PR is included in version 6.7.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants