AI Toolchain Release Monitor - GitHub Release Changes avatar

AI Toolchain Release Monitor - GitHub Release Changes

Pricing

from $0.60 / 1,000 saved observations

Go to Apify Store
AI Toolchain Release Monitor - GitHub Release Changes

AI Toolchain Release Monitor - GitHub Release Changes

Monitor GitHub releases for AI toolchains: tags, prereleases, dates, asset metadata and edited notes. Compare saved releases without downloading binaries.

Pricing

from $0.60 / 1,000 saved observations

Rating

0.0

(0)

Developer

Brandt May

Brandt May

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Features

Limited permissions

Share

AI Toolchain Release Monitor — illustrative workflow

AI Toolchain Release Monitor - GitHub Release Changes

Monitor GitHub releases for AI toolchains: tags, prereleases, dates, asset metadata and edited notes. Compare saved releases without downloading binaries.

Open in Apify Console · First run · Output · Pairings · Price

First run and source setup

  1. Review the source targets and filters before starting. Apify account authorization is required to run the Actor.
  2. Open the JSON input editor and start with the bounded configuration below. Review dates and targets for your intended use.
  3. Review the current Pricing tab and set a maximum run charge and timeout in Run options. A result limit does not set a spending limit or promise that many rows.
  4. After completion, inspect the dataset and the run's diagnostics/Storage records described in the full guide. A successful process alone does not establish complete source coverage.
{
"repositories": [
"ollama/ollama"
],
"maxResults": 5,
"itemsPerQuery": 3
}

Historical evidence for this exact input was recorded 2026-10-18 UTC on build ID Wrdjo4VThqVqaapQY. It is not a fresh source-availability test.

Output worth checking

The published default dataset view includes these fields. Missing values and source-specific coverage are explained in the full guide.

  • title · title
  • repository · repository
  • release Id · releaseId
  • tag Name · tagName
  • published At · publishedAt
  • prerelease · prerelease

Keep original source links and observation dates when interpreting records. JSON preserves nested values; CSV is useful for flat columns.

Use this with other Mayd It Actors

These are separate tools for a reviewed workflow. Each run uses its own input, authorization and pricing; this guide does not configure automatic execution.

GitHub Repository Change Monitor - Stars, Forks & Activity

Track the exact public repository’s metadata, license and activity dates alongside the discovery or release signal.

Parallel research context: Choose the corresponding source target in this second Actor’s own input form; no automatic field transfer is configured. Keep both original source URLs and observation dates in your review sheet; reconcile identities manually.

Keep the distinction: Release tags, repository metadata and support lifecycles are different observations. Match the exact project and release cycle before using them together.

Software Lifecycle Watchlist Monitor

Add vendor-published support deadlines for the exact software products and release cycles that your reviewed stack actually uses.

Parallel research context: Choose the corresponding source target in this second Actor’s own input form; no automatic field transfer is configured. Keep both original source URLs and observation dates in your review sheet; reconcile identities manually.

Keep the distinction: Release tags, repository metadata and support lifecycles are different observations. Match the exact project and release cycle before using them together.

Price and run limits

At the captured FREE-tier rate (2026-11-16 UTC), $0.001 per saved observation. Actor Start is $0.00005 per event; the number of startup events depends on memory. Plan rates and future changes may differ; check the current Pricing tab before starting.

A capped or interrupted run can save useful rows without covering its intended scope. Review the source-specific completeness and comparison rules below before treating missing rows as removals.

Documentation and support

Product guide, source limits and saved output · API and MCP setup · Input schema

Open this Actor's Issues tab with a run URL, the relevant input field and the result you expected. Remove API keys and private information before sharing.

Complete source guide

AI Toolchain Release Monitor - GitHub Release Changes

AI Toolchain Release Monitor - GitHub Release Changes icon

Track release metadata and edited notes, not noisy repository popularity metrics.

Monitor GitHub releases for AI toolchains: tags, prereleases, dates, asset metadata and edited notes. Compare saved releases without downloading binaries.

Start in under a minute

  1. Paste github owner/repository into the first input field, or use the included sample.
  2. Keep the five-result limit for your first run and choose Start.
  3. Open Observations, Scope and diagnostics, or the Readable run report in Output. Export CSV or JSON from the dataset.
{
"repositories": [
"ollama/ollama"
],
"maxResults": 5,
"itemsPerQuery": 3
}

No source account, API key, paid proxy or extra subscription is required for these public endpoints. Source availability and rate limits still apply.

Who this helps

AI platform teams tracking the open-source components they deploy.

A real output sample

Captured in a successful bounded Apify run; arrays and long text are shortened for readability. Values are snapshots, not live guarantees.

{
"recordId": "ollama/ollama:416126438",
"title": "v0.40.7",
"repository": "ollama/ollama",
"releaseId": 416126438,
"tagName": "v0.40.7-rc0",
"publishedAt": "2026-10-18T00:28:57Z",
"prerelease": true,
"assetCount": 17,
"releaseNotesHash": "c5fdcfd3d1467e6d31be89897a61427b0832dadedae653475f7ed18fa202965a",
"url": "https://github.com/ollama/ollama/releases/tag/v0.40.7-rc0",
"observedAt": "2026-10-18T15:20:57.944Z",
"comparisonStatus": "not_requested"
}

What you receive

One row per unique confirmed observation. Every row includes a stable recordId, title, source URL and observation time.

FieldMeaning
repositorySource-reported repository; missing optional values remain null.
releaseIdSource-reported release id; missing optional values remain null.
tagNameSource-reported tag name; missing optional values remain null.
publishedAtSource-reported published at; missing optional values remain null.
prereleaseSource-reported prerelease; missing optional values remain null.
assetCountSource-reported asset count; missing optional values remain null.
releaseNotesHashSource-reported release notes hash; missing optional values remain null.
comparisonStatusnot_requested, new, changed or unchanged
changedFieldsFields different from your last saved observation
previousPrevious saved source values when comparison is enabled

Saved comparisons

Enable Compare with saved observations, choose a snapshot name, and reuse the same input scope. The first run establishes history; it cannot report changes before that point. Enable Save only new or changed observations for later runs if you want a change-only export. An unchanged run can correctly save zero rows.

Only confirmed saved rows advance history. A bounded or failed run never establishes that a missing record was deleted. History is stored in a named key-value store in the running user's account. Use one writer per snapshot: do not overlap runs against the same snapshot. Change the snapshot name when starting a new independent workflow.

Scope and limitations

One GitHub releases page per exact public repository. Includes prereleases and excludes drafts by public API behavior. Tags without GitHub releases are outside scope. Anonymous GitHub rate limits apply. Downloads and release notes do not establish safety or compatibility.

At most ten input values and five hundred saved rows per run. Each input uses a bounded source response. Shared feeds are cached within the run; public documents may require a robots.txt request. Requests are paced. Responses are capped at 8 MiB and share the run deadline. No authentication bypass or code execution is performed. HTTP 429 stops further requests. Source failures appear in SUMMARY and the HTML report, never as paid data rows.

Pricing

The configured base price is $0.001 per saved observation, plus $0.00005 per start at the default memory. Five observations cost $0.00505 at that base rate. Applicable plan discounts and the Store pricing panel govern actual charges. Set a maximum charge in Run options. Diagnostics, reports and unchanged skipped rows are not dataset result events.

A practical workflow

AI platform teams tracking the open-source components they deploy. Track release metadata and edited notes, not noisy repository popularity metrics. Start with the included five-result sample, review source links, then save your own scope as an Actor task. Use a named snapshot for repeat runs and keep source metadata with downstream exports.

Make it recurring

Save an Actor task with your inputs, then attach an Apify Schedule. For change detection, keep the same snapshot and avoid overlapping runs. Add an integration to deliver results to your own spreadsheet or workflow. No external delivery is enabled automatically.

Frequently asked questions

Why did a repeat run return zero rows? With change-only mode enabled, unchanged records are skipped. Check SUMMARY to distinguish this from empty matches, limits, or an upstream error.

Does a missing record mean it was deleted? No. Searches cover a bounded source window; a record can move outside it. Missing records never become deletion claims.

Can I export or integrate the data? Yes. Use Apify dataset exports for CSV/JSON, or the Actor API and your own integrations. No external message or delivery is enabled by default.

Examples

  1. GitHub owner/repository: ollama/ollama — A bounded ollama/ollama observation sample. Review source evidence and export rows or compare them in a later run.
  2. GitHub owner/repository: vllm-project/vllm — A bounded vllm-project/vllm observation sample. Review source evidence and export rows or compare them in a later run.
  3. GitHub owner/repository: langchain-ai/langchain — A bounded langchain-ai/langchain observation sample. Review source evidence and export rows or compare them in a later run.

Source and support

Official source documentation. This independent Mayd IT tool is not affiliated with the source platform. Open an Actor issue with the run ID and expected result, or contact bmay@mayd-it.com. Never include credentials.

Product guide · Workflow and real output · All data tools · Use with AI