IntenseWebs/discourse
3
0
Fork 0
mirror of https://github.com/discourse/discourse.git synced 2024-11-22 08:57:10 -06:00
Code Issues Packages Projects Releases Wiki Activity

DEV: upgrades sassc to 2.4.0 (#10447)

Browse Source 
We were stuck on 2.0.1 but multiple reports on the original issue shows that the issue has been fixed since 2.3 and 2.4:

https://github.com/sass/sassc-ruby/issues/146#issuecomment-654522157
https://github.com/sass/sassc-ruby/issues/146#issuecomment-654522157

There's one report show it was not fixed in 2.3.0, but that's the only one, it's probably worth trying: https://github.com/sass/sassc-ruby/issues/146#issuecomment-639073736
This commit is contained in:
Joffrey JAFFEUX 2020-08-21 13:46:46 +02:00 committed by GitHub
parent 106a2f58a2
commit 2fac77cc48
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Gemfile
View File

@ -218,9 +218,7 @@ gem 'logstash-event', require: false
gem 'logstash-logger', require: false
gem 'logster'
# NOTE: later versions of sassc are causing a segfault, possibly dependent on processer architecture
# and until resolved should be locked at 2.0.1
gem 'sassc', '2.0.1', require: false
gem 'sassc', '2.4.0', require: false
gem "sassc-rails"
gem 'rotp', require: false

5
Gemfile.lock
View File

@ -376,9 +376,8 @@ GEM
crass (~> 1.0.2)
nokogiri (>= 1.8.0)
nokogumbo (~> 2.0)
sassc (2.0.1)
sassc (2.4.0)
ffi (~> 1.9)
rake
sassc-rails (2.1.2)
railties (>= 4.0.0)
sassc (>= 2.0)
@ -544,7 +543,7 @@ DEPENDENCIES
ruby-prof
ruby-readability
rubyzip
sassc (= 2.0.1)
sassc (= 2.4.0)
sassc-rails
seed-fu
shoulda-matchers