back off sass-rails specificity #18

Merged
merged 1 commit into from Dec 23, 2011

Conversation

Projects
None yet
4 participants
Contributor

bkerley commented Dec 20, 2011

Is there a way to test this against the newer versions of sass-rails?

Member

thomas-mcdonald commented Dec 22, 2011

I imagine this will work straight with me merging it and pushing a new release right now but I'm tired, which means it's probably a really bad thing to do right this minute.

I'll get to this first thing in the morning.

Contributor

rwjblue commented Dec 23, 2011

If I'm reading this correctly this will allow bootstrap-sass to use sass-rails 3.2, correct?

zazena commented Dec 23, 2011

Just ran into this myself. Rails v3.2rc1 has sass-rails v3.2.2 as a dep.

Member

thomas-mcdonald commented Dec 23, 2011

@rjackson That's my understanding of it, I had to look up the exact definition myself. ~> 3.1.0 locks to 3.1.x, while ~> 3.1 locks to 3.x, where x > 1.

@thomas-mcdonald thomas-mcdonald pushed a commit that referenced this pull request Dec 23, 2011

Thomas McDonald Merge pull request #18 from bkerley/master
back off sass-rails specificity
e0ef338

@thomas-mcdonald thomas-mcdonald merged commit e0ef338 into twbs:master Dec 23, 2011

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