Open
Conversation
This was referenced Mar 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
irb/notifierusage appears to just be debug logs that are never actually activated since they aren't linked up to YARD's own logging system.The dependency on it therefore seems unnecessary and looks safe to remove, fixing compatibility with Ruby 4.0.
Normally this would only be a problem with the legacy parser but overload tag parsing still unconditionally uses the legacy parser only:
yard/lib/yard/tags/overload_tag.rb
Lines 58 to 60 in eddd10c
Fixes #1636
Fixes #1645
Completed Tasks
bundle exec rakelocally (if code is attached to PR).