GitLab Releases Delta Monitor
Pricing
from $1.00 / 1,000 new gitlab releases
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
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
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_SEENwith zero PPE delta charges - Optional private token — higher rate limits / private projects; public projects work without one
- Self-hosted ready — optional
gitlabHostfor your GitLab instance - Schedule-friendly — pair with an Apify schedule for continuous monitoring
Input
| Field | Required | Description |
|---|---|---|
projects | yes | List of group/project paths (nested ok) or numeric project IDs |
privateToken | no | GitLab PAT / project token (secret) as PRIVATE-TOKEN |
gitlabHost | no | API root (default https://gitlab.com/api/v4) |
sinceTag | no | On first run for a project, treat this tag and older as already seen |
maxPages | no | Max release API pages per project (default 2) |
includeUpcoming | no | Include GitLab upcoming_release items (default true) |
resetState | no | Clear 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
| Situation | Dataset items | release-delta charges |
|---|---|---|
Empty state, no sinceTag | 0 | 0 (baseline only) |
Empty state + sinceTag | Only newer than that tag | 1 per item |
| Later runs | New tag fingerprints only | 1 per item |
Tips
- Run once to baseline, then attach a schedule (e.g. hourly/daily).
- Add a
privateTokenif you monitor many projects or private ones (unauthenticated rate limits are lower). - Set a user max total charge on the run so costs stay predictable.
- For self-hosted GitLab, set
gitlabHostto 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.