Skip to content

Conversation

@TBK145
Copy link

@TBK145 TBK145 commented Sep 15, 2025

So it can be used with newer versions and doesn't need to be updated every time

Copy link
Member

@onno-vos-dev onno-vos-dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will allow for version 4, 5 or any other major breaking change to be included? Wouldn't it be better to just add another or if what you're after is s newer version? This seems like quite a big change to me considering major version 5 is out as of now (I haven't checked the changelog but I'd imagine a bump to v4 and v5 to potentially come with breaking changes) that would go untested in any pipeline?

@TBK145
Copy link
Author

TBK145 commented Sep 24, 2025

Hi! I understand the what you're saying, The changes in 4.0 and 5.0 seemed relatively small to me and to prevent having to update this file again when another major version is released I added the >= instead or the or.
But if you want I can change it back and add the additional ors.

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.

2 participants