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

Stylelint 13 #25

Merged
merged 1 commit into from
Jan 24, 2020
Merged

Stylelint 13 #25

merged 1 commit into from
Jan 24, 2020

Conversation

limonte
Copy link

@limonte limonte commented Jan 19, 2020

@silverwind
Copy link

silverwind commented Jan 24, 2020

Can we just make it >=7.0.0? It'd be less maintenance required if it is reasonable to expect compatibility.

@limonte
Copy link
Author

limonte commented Jan 24, 2020

Can we just make it >=7.0.0? It'd be less maintenance required if it is reasonable to expect compatibility.

It's unreasonable to expect compatibility in major releases per their definition:

MAJOR version when you make incompatible API changes

Read more about semver: https://semver.org/

@silverwind
Copy link

Thanks, I know about semver. Up to the maintainer of course. I'd personally trust stylelint to not have breaking API changes in their next major releases.

@limonte
Copy link
Author

limonte commented Jan 24, 2020

I'd personally trust stylelint to not have breaking API changes in their next major releases.

Why would they make major releases without breaking API changes?

@silverwind
Copy link

I meant relevant breaking changes, but whatever I hope this gets merged soon.

@lahmatiy lahmatiy merged commit 26fc504 into csstree:master Jan 24, 2020
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