Future of (development) dependency for byebug?

Currently for power_assert testsuite, it depends on byebug:
https://github.com/ruby/power_assert/blob/297fa68908c45c4ca6c41e0940ebcc069744d580/power_assert.gemspec#L26
https://github.com/ruby/power_assert/blob/297fa68908c45c4ca6c41e0940ebcc069744d580/test/trace_test.rb#L10

So can I rely on byebug?

Why I am asking here is that

• The last activity on https://github.com/deivid-rodriguez/byebug seems more than 2 years ago.
• And it seems that with ruby 3.3 (I tested https://github.com/ruby/ruby/commit/cd67c0d2040f1ade0fe8b1533816281553bfe6e6 ) byebug testsuite fails , and looks like byebug does not work with ruby 3.3 properly.

So I think if power_assert is going to use byebug, someone has to support byebug maintainership.
Or can power_assert be switched to use debug gem?

power_assert.gemspec の 26 行目にある依存関係の宣言と、test/trace_test.rb の 10 行目にある byebug の使用から始めます。報告された Ruby 3.3 でのテスト失敗を確認し、既存のテストスイートで代わりに debug gem を使用できるか比較します。合意された互換性のある依存関係が決まり、テストが成功すれば完了です。