Change PostCSS version strategy #471
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It is indeed a lot of work, I think we can just leave it to be and it will go gradually, if it becomes an issue at any point we can just release that plugin in particular. Do you foresee any issues there? |
Not really. I think this change is the better versioning strategy but I don't think there currently is an urgent need to have it out there. Rolling it out one by one will also not cause any issues as we are relaxing the version constraint. |
…cy-version-lint--adaptable-sea-lion-f22ee39be1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #465
Should we release all the plugins?
Feels like a lot of work for something that isn't a reported issue.