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
Crates.io is missing published rubydex 0.3.0 version #978
Hey Marco, what's the crate you plan to use? At this moment I'd recommend building on top of the Ruby gem instead of the Rust crates if possible.
A bit of context: we currently prioritize Ruby interface and will expose features mostly through Ruby API or Ruby gem's executable rdx. This is because:
Without Ruby, we can't effectively load the right Ruby version for the project, nor setup the bundle correctly. And the result is that pure Rust implementation is likely limited to seeing the project's own codebase. This is why we moved MCP server from Rust to Ruby
We're building Rubydex-based tools (linter, complexity analyzer...etc.) directly into Rubydex. And by building in Ruby, it's easier for people to reuse code and contribute
It doesn't mean we want to abandon Rust crates, just that we can't prioritize them now.
I have been experimenting with Rubydex to be able to power the static analysis part for what I need in Herb here: marcoroth/herb#1993
Part of Herb's tooling is written in Rust, including (now) part of the linter, which is why I was looking to build this analysis in Rust so that it could just use it a regular dependency without having to rely on Ruby. I'm looking to more accurately trace through view files for more advanced and accurate cross-file diagnostics.
There is a good chance that part of this work even belongs in Rubydex itself, but at this point I just wanted to get more familiar with the Rubydex internals to see what it can power today.
Hey @marcoroth, the Rust crates are now published alongside the gem. rubydex and rubydex-sys are on 0.4.3, and from now on the gem and both crates are released together using trusted publishing.
Closing this, but let us know if anything is off when you pull the crate into Herb.
Activity
[-]Crates.io is missing Rubydex 0.3.0[/-][+]Crates.io is missing published rubydex 0.3.0 version[/+]st0012 commentedon Aug 4, 2026
Hey Marco, what's the crate you plan to use? At this moment I'd recommend building on top of the Ruby gem instead of the Rust crates if possible.
A bit of context: we currently prioritize Ruby interface and will expose features mostly through Ruby API or Ruby gem's executable
rdx. This is because:It doesn't mean we want to abandon Rust crates, just that we can't prioritize them now.
marcoroth commentedon Aug 4, 2026
Hey @st0012, thanks for the quick reply!
I have been experimenting with Rubydex to be able to power the static analysis part for what I need in Herb here: marcoroth/herb#1993
Part of Herb's tooling is written in Rust, including (now) part of the linter, which is why I was looking to build this analysis in Rust so that it could just use it a regular dependency without having to rely on Ruby. I'm looking to more accurately trace through view files for more advanced and accurate cross-file diagnostics.
There is a good chance that part of this work even belongs in Rubydex itself, but at this point I just wanted to get more familiar with the Rubydex internals to see what it can power today.
alexcrocha commentedon Oct 26, 2026
Hey @marcoroth, the Rust crates are now published alongside the gem. rubydex and rubydex-sys are on
0.4.3, and from now on the gem and both crates are released together using trusted publishing.Closing this, but let us know if anything is off when you pull the crate into Herb.
marcoroth commentedon Oct 26, 2026
Awesome, will do. Thanks @alexcrocha! 🙏🏼