pin lessc to 1.4 #5027
Merged
pin lessc to 1.4 #5027
Conversation
This file contains 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
Not necessarily what we want to do, but every minor revision of less seems to change how it minifies, which produces churn. At least this should prevent accidental churn, as has recently been committed to master.
|
Great, I will try this out and use it to help me get the right version of less... |
|
This looks great, merging. |
|
I could have added a note for how to install a pinned version: |
|
That might be a good idea. |
mattvonrocketstein
pushed a commit
to mattvonrocketstein/ipython
that referenced
this pull request
Nov 3, 2014
pin lessc to 1.4
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.
Not necessarily what we want to do, but every minor revision of less seems to change how it minifies, which produces churn in supposedly small changes.
At least this should prevent accidental churn, as has recently been committed to master.
My vague plan has been to update less when we switch to bootstrap 3, since that will certainly make big changes to the css product anyway.