Skip to content

Conversation

@taketo1113
Copy link

@taketo1113 taketo1113 commented Nov 5, 2025

This Pull Request pins power_assert to v2.x, as power_assert has dropped support for Ruby < 3.1.

Since power_assert v3.0.0 has dropped support for Ruby 3.1 and earlier, but its gemspec does not specify required_ruby_version, the following error occurs in CI.
(Even if required_ruby_version is added in power_assert 3.0.1, Ruby 3.1 and earlier would still install version 3.0.0, so pinning to power_assert v2.x remains necessary.)

Run rake test
D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/gems/2.7.0/gems/power_assert-3.0.0/lib/power_assert/parser.rb:106: warning: Pattern matching is experimental, and the behavior may change in future versions of Ruby!
D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/gems/2.7.0/gems/power_assert-3.0.0/lib/power_assert/parser.rb:106: warning: Pattern matching is experimental, and the behavior may change in future versions of Ruby!
D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/2.7.0/win32/registry.rb:416:in `private_class_method': undefined method `new' for class `#<Class:Win32::Registry>' (NameError)
Did you mean?  next
	from D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/2.7.0/win32/registry.rb:416:in `<class:Registry>'
	from D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/2.7.0/win32/registry.rb:74:in `<module:Win32>'
	from D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/2.7.0/win32/registry.rb:4:in `<top (required)>'
	from D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	from D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	from D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/2.7.0/win32/resolv.rb:7:in `<top (required)>'
	from D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	from D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	from D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/2.7.0/resolv.rb:171:in `<class:Hosts>'
	from D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/2.7.0/resolv.rb:168:in `<class:Resolv>'
	from D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/2.7.0/resolv.rb:38:in `<top (required)>'
	from D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	from D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	from D:/a/net-http/net-http/lib/net/http.rb:25:in `<top (required)>'
	from D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	from D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	from D:/a/net-http/net-http/test/net/http/test_buffered_io.rb:3:in `<top (required)>'
	from D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	from D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	from D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/gems/2.7.0/gems/rake-13.3.1/lib/rake/rake_test_loader.rb:21:in `block in <main>'
	from D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/gems/2.7.0/gems/rake-13.3.1/lib/rake/rake_test_loader.rb:6:in `select'
	from D:/a/_temp/rubyinstaller-2.7.8-1-x64/lib/ruby/gems/2.7.0/gems/rake-13.3.1/lib/rake/rake_test_loader.rb:6:in `<main>'
rake aborted!
Command failed with status (1)

https://github.com/taketo1113/net-http/actions/runs/19091270166/job/54542337643#step:5:26

@taketo1113 taketo1113 changed the title CI: Pin power_assert to v2.x to drop support for Ruby < 3.1 CI: Pin power_assert to v2 as power_assert v3 has dropped support for Ruby < 3.1. Nov 5, 2025
@taketo1113
Copy link
Author

taketo1113 commented Nov 5, 2025

Since this issue has been fixed in power_assert v3.0.1, the pin to power_assert v2 is no longer necessary, so this Pull Request will be closed.

@taketo1113 taketo1113 closed this Nov 5, 2025
@taketo1113 taketo1113 deleted the fix-ci branch November 5, 2025 23:41
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.

1 participant