RubyGems Release Monitor API

RubyGems Release Monitor API collects clean, structured package release data from the public RubyGems API. Use it to track gem updates, monitor dependency changes, and feed release metadata into analytics, alerts, or AI workflows.

Why use this RubyGems release monitor?

Ruby libraries change constantly, and version bumps can matter just as much as code changes. This actor gives you a simple way to watch gems without wiring together custom polling and parsing logic.

Typical use cases:

• Track release cadence for critical Ruby dependencies
• Monitor newly published versions in a dependency stack
• Power alerts, dashboards, and changelog workflows
• Enrich engineering data pipelines with package metadata

Features

• Monitor one or more RubyGems packages in a single run
• Return either a compact latest-release summary or individual recent version records
• Include package metadata, release timestamps, authors, licenses, and dependency counts
• Pay-per-event pricing tied to the records you actually use

Input

Example: quick latest-release check

{
  "gems": "rails, rack, nokogiri",
  "latestOnly": true,
  "maxResults": 5,
  "versionsPerGem": 10
}

Example: recent version monitoring

{
  "gems": "rails, sidekiq",
  "latestOnly": false,
  "maxResults": 20,
  "versionsPerGem": 5
}

Input fields

Field	Type	Description
gems	string	Comma or newline separated RubyGems package names to monitor, such as rails or nokogiri.
latestOnly	boolean	When enabled, returns one summary record per gem instead of version records.
maxResults	integer	Maximum number of dataset records to return across all gems. Values above 100 are clamped.
versionsPerGem	integer	How many recent versions to include for each gem when latestOnly is turned off. Values above 50 are clamped.

Output

Example record: latest-release summary

{
  "gemName": "rails",
  "version": "8.0.2",
  "latestVersion": "8.0.2",
  "summary": "Ruby on Rails is a web framework",
  "description": "Ruby on Rails is a web framework",
  "homepageUrl": "https://rubyonrails.org/",
  "sourceCodeUrl": "https://github.com/rails/rails",
  "documentationUrl": "https://api.rubyonrails.org/",
  "gemUrl": "https://rubygems.org/gems/rails",
  "authors": "David Heinemeier Hansson",
  "licenses": ["MIT"],
  "createdAt": "2026-05-26T00:00:00.000Z",
  "prerelease": false,
  "platform": "ruby",
  "downloads": 1234,
  "runtimeDependenciesCount": 24,
  "developmentDependenciesCount": 0,
  "recentVersionCount": 0,
  "recordType": "package_summary"
}

Example record: version detail

{
  "gemName": "rails",
  "version": "8.0.2",
  "latestVersion": "8.0.2",
  "summary": "Ruby on Rails is a web framework",
  "description": "Ruby on Rails is a web framework",
  "homepageUrl": "https://rubyonrails.org/",
  "sourceCodeUrl": "https://github.com/rails/rails",
  "documentationUrl": "https://api.rubyonrails.org/",
  "gemUrl": "https://rubygems.org/gems/rails",
  "authors": "David Heinemeier Hansson",
  "licenses": ["MIT"],
  "createdAt": "2026-05-26T00:00:00.000Z",
  "prerelease": false,
  "platform": "ruby",
  "downloads": 1234,
  "runtimeDependenciesCount": 24,
  "developmentDependenciesCount": 0,
  "recentVersionCount": 1,
  "recordType": "version_record"
}

Limits and caveats

• Package names must point to public RubyGems packages.
• If a package has many releases, use latestOnly=true for a cheaper summary run.
• maxResults is capped at 100 to keep runs predictable and affordable.
• versionsPerGem is capped at 50 so detail runs stay fast.

Pricing

This actor uses Pay-Per-Event pricing.

Event	Price	Charged when
package-summary-produced	$0.25 / 1k	A latest-release summary record is produced
version-record-produced	$0.75 / 1k	An individual version record is produced

FAQ

Do I need a RubyGems account?
No. The actor reads public RubyGems metadata.

What is the difference between summary mode and detail mode?
Summary mode returns one record per gem using the latest published version. Detail mode returns recent versions as separate records.

Can I use this for dependency monitoring?
Yes. Re-run the actor on a schedule and compare version changes over time.

What if a gem does not exist?
The actor skips invalid package names and continues with the rest of the list.