Fix build on Ruby 3.2 #573
Merged
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.
Signed-off-by: James Couball jcouball@yahoo.com
Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.
Description
This PR fixes the ruby-head build (Ruby 3.2) which fails because
yard
calls Ruby'staint
API. lsegal/yard#1419 fixes this issue inyard
which was merged months ago but there has not yet been a new release ofyard
.Rather than live with the
ruby-head
builds failing for thegit
gem, this PR installsyard
from the Githubmain
branch. This is a temporary work around which should be removed afteryard
releases a new version that includes the fix fortaint
.More info on the
taint
API in Ruby:In Ruby 2.7, the taint checking mechanism was removed.
Object#taint
,Object#trust
,Object#untaint
,Object#untrust
and related functions in the C-API have been made no-op methods. It means they do nothing and just return self.In Ruby 3.2,
Object#taint
,Object#trust
,Object#untaint
,Object#untrust
and the C functions have been completely removed.