How do I connect RubyGems to Lodol?

Authenticate RubyGems once from your workspace and every action and trigger it supports becomes available to drop into a workflow. There is no glue code to write or maintain.

All integrations

RubyGems

Code Repositories

Read anything on RubyGems.org. Look a gem up by name for its licence, authors, links and dependencies, walk its whole release history, open one release for its files, checksums and signed attestations, and see who can push to it. Search the registry, watch what has been published in the last week, find which gems depend on one you care about, and track download counts for a release, a gem or the whole site. No account or API key is required.

Get Started Browse all integrations

18 actions

Actions

Steps your workflow can run in RubyGems.

Get a gemLook up a gem on RubyGems.org: what it does, who wrote it, what licence it carries, where its source, issues and changelog live, what it depends on, and how often it has been downloaded. Everything is at the gem's newest release; use 'Get a gem version' to read an older one. No API key required.

Search gemsSearch RubyGems.org exactly as its own search box does, across gem names and descriptions. Results come back 30 to a page with each gem's version, licence, author and download count, and the answer says whether another page follows. Use 'Find gem names' when you only need names. No API key required.

Find gem namesFind gem names that match some text, from the same lookup that fills the search box on RubyGems.org. Names only, which is what 'is there a gem called something like this?' asks and what feeds a gem field in a later step. The answer says whether one of them matched exactly. No API key required.

List dependent gemsList the gems whose newest release depends on this one, which is the blast radius of a change or a security issue. Narrow it to gems that need this one to run, or only to build and test. No API key required.

List gem versionsList a gem's releases with the date each went out, how many times it was downloaded and which Ruby it needs. Versions order by RubyGems' own rules rather than as text, so 1.10.0 sits above 1.9.0 and a release above its own release candidates. Only indexed releases are listed, so a yanked one is absent. No API key required.

Get the latest versionGet just the newest version number of a gem, and nothing else. The cheapest way to answer 'is the version we pin behind?', so it is the step to put on a schedule to watch a dependency. No API key required.

Get a gem versionRead one specific release of a gem in full: its summary and description, when it was built and published, the Ruby and RubyGems versions it needs, its dependencies and its checksums. Use it to read the release a project actually pins rather than whatever is newest today. No API key required.

List the files in a versionList every file packaged inside one release, each with its SHA-256. The check for 'did this release ship the file I expect, unchanged?'. RubyGems only records this for releases pushed since it started keeping file manifests, so a much older release reports that its contents are unavailable. No API key required.

Get a version's attestationsGet the sigstore attestations published with a release: proof, signed when the gem was pushed and recorded in a public transparency log, of what was published and by which build. The supply chain check for a dependency. Signing is opt-in and recent, so an empty answer is normal rather than a failure. No API key required.

List releases in a timeframeList every release published anywhere on RubyGems.org between two moments. Give it the moment your last run finished and only what has appeared since comes back, so a scheduled workflow sees each release exactly once. RubyGems answers at most seven days at a time. No API key required.

Get total downloadsGet how many gems have ever been downloaded from RubyGems.org, across every gem and every version. One number for the whole registry, which is the context a single gem's count needs. No API key required.

Get downloads for a versionGet how often one release of a gem was downloaded, and how often the gem has been downloaded in total. Both numbers come back together with the release's share worked out, so a step can report adoption of a new version without a second call. No API key required.

List the most downloaded gemsList the fifty most downloaded gem versions on RubyGems.org, ranked, each with its size, licence and publish date. The picture of what the Ruby ecosystem actually runs on. No API key required.

List a user's gemsList every gem a RubyGems user can push to, with each gem's newest version and download count and the total across all of them. Public, so it works for anyone's username. Use 'List my gems' for the account this connection's key belongs to. No API key required.

List gem ownersList everyone who can push releases of a gem, and in what role: an owner can also manage who else may, a maintainer can only push. Works for any gem, not just your own. An email address shows only for people who chose to publish theirs. No API key required.

Get a user profileGet a RubyGems user's public profile. Takes a username or the numeric id that appears on a gem's owner list, so it is the step that turns an id into a name a person recognises. No API key required.

List new gemsList the fifty gems most recently published to RubyGems.org for the very first time. These are names that did not exist before, which is what a typosquat watch or a 'what is new in Ruby' digest wants. Use 'List updated gems' for new versions of gems that already existed. No API key required.

List updated gemsList the fifty most recent releases published anywhere on RubyGems.org, newest first. Use 'List releases in a timeframe' instead when a scheduled run needs to see every release exactly once rather than the latest fifty. No API key required.