GitHub Release History Export

Collect published release notes for up to three exact public repositories and an inclusive UTC publication-date window. Review intervening upstream changes or feed source notes into your own ticket/LLM workflow. Notes are untrusted source material, not instructions or compatibility advice.

Input

repositories: 1–3 owner/name public GitHub identities, default ["cli/cli"]. Case-insensitive duplicates collapse; arbitrary URLs, tokens and unknown keys fail before networking. publishedFrom/publishedTo: valid inclusive UTC YYYY-MM-DD dates, default 2026-09-01..2026-09-30. includePrereleases: boolean, default true. maxSafetyItems: 1–500, default500; fail rather than truncate when matching rows exceed it. Normal nondefault example: psf/requests, 2025-01-01..2026-10-15. Caller chooses dates; there is no automatic installed-version or commit-range resolution.

Output

One github_release row per unique release: repository, numeric releaseId, tagName, sanitized name, publishedAt, createdAt, source prerelease flag, notesMarkdown, notesPresent, sourceUrl, licenseUrl and retrievedAt. Notes preserve Markdown except contact/secret/mention redaction; empty notes remain empty and notesPresent=false. Sorted by repository then publication time and release ID ascending. Metadata author/profile/uploader objects are excluded. COVERAGE/SUMMARY/RUN-SUMMARY are uncharged key-value records. No matching releases is an explicit no-matching-results failure with coverage, no rows/events. Bare tags, drafts, private repos, assets/binaries, commit diffs and generated release notes are outside scope. Review repository licenses before reusing notes; licenseUrl is a reference and is not itself fetched.

Limits

Every repository is fully paged in groups of50, up to ten pages (500source releases/repository). Traversal never stops on a date cutoff because source ordering is not assumed. A remaining next page fails refine-required, even if the selected date window is narrow: use a smaller-history repository; narrowing dates only helps the output cap. Recheck first page IDs/publication state after traversal; duplicates or detected drift fail. Concurrent source edits can still prevent a transactionally stable snapshot; coverageComplete describes the observed traversal only. Three repos,34HTTP requests including robots and drift checks; 15sec request timeout,180sec acquisition,90sec delivery,4MiB response wire/decoded,64MiB aggregate transfer/decoded,24MiB staged result,256MB. No retries/redirects, auth/cookies/proxy/browser or paid dependency. Only first-party API routes are fetched; current robots and public DNS pinning apply. 403 quota exhaustion/429, authentication, timeouts, malformed data, identity changes and caps fail visibly before delivery.

Pricing

Published price: $0.001 per unique release-delivered primary event, with no start or trial charge. Private cloud probes verified 4/4 default, 7/7 alternate and 63/63 maximum-load dataset rows to primary events. Acquire/validate the entire selected result before delivery. PPE allowance must cover every row and is rechecked before each <=50-row SDK push; short charged acknowledgements fail. Non-PPE stores rows with zero charge. Source failure and coverage metadata are uncharged. SDK writes have no whole-run rollback; earlier batches may remain if a later delivery fails. Private cloud runs confirmed primary event counts; platform compute cost remains separate. Repeated runs charge delivered rows again.

Privacy

Only public repository release content is exported. Exclude author/profile/uploader/contact fields; redact email/phone/common secret patterns and @mentions from notes and names. No credentials, cookies, private access or linked URL retrieval. Redaction is pattern-based and not a guarantee of detecting every possible personal datum. GitHub is the source and does not endorse this Actor.