Skip to content

Comments

Update Prism to 1.4.0 and remove workarounds#312

Merged
mame merged 2 commits intoruby:masterfrom
x-smasato:prism-1.4.0
Apr 28, 2025
Merged

Update Prism to 1.4.0 and remove workarounds#312
mame merged 2 commits intoruby:masterfrom
x-smasato:prism-1.4.0

Conversation

@smasato
Copy link
Contributor

@smasato smasato commented Apr 27, 2025

This PR updates the Prism dependency from 1.0.0 to 1.4.0 and removes workarounds that were needed for the old version.

Copy link
Member

@mame mame left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since Ruby 3.4 bundles prism 1.2.0 by default, I was wondering that I should get stuck with prism 1.2.0... But If I asked myself "should I add a CI matrix for prism 1.2.0?", I don't want so. So I will merge it!

@mame mame merged commit afefd34 into ruby:master Apr 28, 2025
7 checks passed
@smasato smasato deleted the prism-1.4.0 branch April 28, 2025 03:54
gemmaro added a commit to gemmaro/typeprof that referenced this pull request Nov 3, 2025
* typeprof.gemspec:, Gemfile, Gemfile.lock: Using TypeProf as a
library does not resolve Gemfile dependencies, so move Prism to
gemspec file.  Notice that TypeProf now uses Prism version 1.4.0 or
later[1].

[1] Update Prism to 1.4.0 and remove workarounds,
    ruby#312
mame pushed a commit that referenced this pull request Nov 4, 2025
* typeprof.gemspec:, Gemfile, Gemfile.lock: Using TypeProf as a
library does not resolve Gemfile dependencies, so move Prism to
gemspec file.  Notice that TypeProf now uses Prism version 1.4.0 or
later[1].

[1] Update Prism to 1.4.0 and remove workarounds,
    #312
mame pushed a commit that referenced this pull request Nov 4, 2025
* typeprof.gemspec:, Gemfile, Gemfile.lock: Using TypeProf as a
library does not resolve Gemfile dependencies, so move Prism to
gemspec file.  Notice that TypeProf now uses Prism version 1.4.0 or
later[1].

[1] Update Prism to 1.4.0 and remove workarounds,
    #312
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants