Skip to content

Commit fcf2bd2

Browse files
[8.16] Pin rubocop-ast development gem due to new dep on prism (backport #17407) (#17427)
* 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 9e583a4 commit fcf2bd2

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
@@ -808,7 +808,7 @@ GEM
808808
rubocop-ast (>= 1.32.2, < 2.0)
809809
ruby-progressbar (~> 1.7)
810810
unicode-display_width (>= 2.4.0, < 3.0)
811-
rubocop-ast (1.32.3)
811+
rubocop-ast (1.42.0)
812812
parser (>= 3.3.1.0)
813813
ruby-maven-libs (3.9.9)
814814
ruby-progressbar (1.13.0)

Gemfile.template

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

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

0 commit comments

Comments
 (0)