Skip to content

Commit d70feb2

Browse files
[8.17] Pin rubocop-ast development gem due to new dep on prism (backport #17407) (#17426)
* Pin rubocop-ast development gem due to new dep on prism (#17407) The rubocop-ast gem just introduced a new dependency on prism. - https://rubygems.org/gems/rubocop-ast/versions/1.43.0 In our install default gem rake task we are seeing issues trying to build native extensions. I see that in upstream jruby they are seeing a similar problem (at least it is the same failure mode jruby/jruby#8415 This commit pins rubocop-ast to 1.42.0 which is the last version that did not have an explicit prism dependency. (cherry picked from commit 6de59f2) * Bump rubocop-ast We are pinning rubocop-ast to the last version that did not require prism. It is a development gem and should not change any behavior of LS. --------- Co-authored-by: Cas Donoghue <[email protected]>
1 parent 7286fe7 commit d70feb2

File tree

2 files changed

+3
-1
lines changed

2 files changed

+3
-1
lines changed

Gemfile.jruby-3.1.lock.release

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -789,7 +789,7 @@ GEM
789789
rubocop-ast (>= 1.36.2, < 2.0)
790790
ruby-progressbar (~> 1.7)
791791
unicode-display_width (>= 2.4.0, < 4.0)
792-
rubocop-ast (1.36.2)
792+
rubocop-ast (1.42.0)
793793
parser (>= 3.3.1.0)
794794
ruby-maven-libs (3.9.9)
795795
ruby-progressbar (1.13.0)

Gemfile.template

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,8 @@ gem "stud", "~> 0.0.22", :group => :build
2626
gem "fileutils", "~> 1.7"
2727

2828
gem "rubocop", :group => :development
29+
# rubocop-ast 1.43.0 carries a dep on `prism` which requires native c extensions
30+
gem 'rubocop-ast', '= 1.42.0', :group => :development
2931
gem "belzebuth", :group => :development
3032
gem "benchmark-ips", :group => :development
3133
gem "ci_reporter_rspec", "~> 1", :group => :development

0 commit comments

Comments
 (0)