GitLab Releases Delta Monitor avatar

GitLab Releases Delta Monitor

Pricing

from $1.00 / 1,000 new gitlab releases

Go to Apify Store
GitLab Releases Delta Monitor

GitLab Releases Delta Monitor

Monitors public GitLab projects for new releases via the official REST API and emits only deltas. First run baselines without charging. PPE event: release-delta.

Pricing

from $1.00 / 1,000 new gitlab releases

Rating

0.0

(0)

Developer

Collin Reynolds

Collin Reynolds

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Share

Watch public GitLab projects for new releases via the official REST API. Only deltas since the last run are written to the dataset — ideal for scheduled monitoring across gitlab.com or self-hosted instances.

Status: Local unpublished scaffold (not yet on the Apify Store). Same baseline-safe PPE shape as the live GitHub Releases Delta Monitor.

Pricing (pay per event, planned): charged mainly for each new GitLab release detected (release-delta, suggested $0.001). First run baselines quietly (0 dataset items / 0 delta charges) so you are not billed for history.

Why use this

  • API-only — official GitLab Releases REST API; no HTML scraping of the gitlab.com UI
  • Delta-only — subsequent runs emit new releases only
  • First-run safe — empty state seeds LAST_SEEN with zero PPE delta charges
  • Optional private token — higher rate limits / private projects; public projects work without one
  • Self-hosted ready — optional gitlabHost for your GitLab instance
  • Schedule-friendly — pair with an Apify schedule for continuous monitoring

Input

FieldRequiredDescription
projectsyesList of group/project paths (nested ok) or numeric project IDs
privateTokennoGitLab PAT / project token (secret) as PRIVATE-TOKEN
gitlabHostnoAPI root (default https://gitlab.com/api/v4)
sinceTagnoOn first run for a project, treat this tag and older as already seen
maxPagesnoMax release API pages per project (default 2)
includeUpcomingnoInclude GitLab upcoming_release items (default true)
resetStatenoClear LAST_SEEN and re-baseline (0 emits that run)

Example

{
"projects": ["gitlab-org/cli", "gitlab-org/gitlab"],
"maxPages": 2,
"includeUpcoming": true,
"resetState": false
}

Output

Each dataset item is a newly detected release, for example:

  • project, tag, name, published_at, html_url, is_upcoming

First-run behavior

SituationDataset itemsrelease-delta charges
Empty state, no sinceTag00 (baseline only)
Empty state + sinceTagOnly newer than that tag1 per item
Later runsNew tag fingerprints only1 per item

Tips

  1. Run once to baseline, then attach a schedule (e.g. hourly/daily).
  2. Add a privateToken if you monitor many projects or private ones (unauthenticated rate limits are lower).
  3. Set a user max total charge on the run so costs stay predictable.
  4. For self-hosted GitLab, set gitlabHost to your instance URL.

ToS / scope

Uses GitLab’s official REST API only (GET /projects/:id/releases). See ./AGREEMENT.md. Respect instance rate limits and terms.