You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Please cut a release (v0.4.8) including #250 — enclosing_range on definition Occurrences #253
Would you consider cutting a new release (v0.4.8) that includes #250 — "Populate enclosing_range on SCIP definition Occurrences" (merged 2026-07-02, 91bcb11)?
Why
enclosing_range on definition occurrences is what lets a SCIP consumer attribute a reference to its enclosing definition — i.e. reconstruct the caller graph ("who calls this method / references this constant"). Without it, references / impact / call-hierarchy queries over a scip-ruby index return no callers even for fully-resolved references.
#250 fixes exactly this, but the latest published release is v0.4.7 (2025-11-07), which predates the merge by ~8 months. Downstream tools that install the released binary (rather than building Sorbet/scip-ruby from source) can't pick up the fix until it's in a tagged release.
Ask
A tagged v0.4.8 built from current master would make #250 available to binary consumers. It looks like releases are workflow-driven (release.yml), so hopefully this is a low-lift ask.
Happy to validate a release candidate against a large (~1,500-file), fully-untyped Rails app if that would help — I can confirm enclosing_range populates and that the caller graph resolves as expected.
Activity
linear commentedon Aug 1, 2026
OSS-24219
christoph-sg commentedon Sep 7, 2026
v0.4.8includes #250dreddnafious commentedon Sep 7, 2026