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?

Commencez par la déclaration de dépendance dans power_assert.gemspec à la ligne 26 et l’utilisation de byebug dans test/trace_test.rb à la ligne 10. Vérifiez l’échec de test signalé avec Ruby 3.3 et comparez si la suite existante peut utiliser le debug gem à la place ; le travail est considéré comme terminé lorsqu’une dépendance compatible fait l’objet d’un accord et que les tests passent.