Skip to content

feat(changelog): ingest GitHub releases and RSS changelog feeds #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
CrisSTEM merged 2 commits into from
Apr 16, 2026
Merged

feat(changelog): ingest GitHub releases and RSS changelog feeds #41

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0d9c096
chore(repo): normalize docs whitespace
CrisSTEM Apr 16, 2026
3f8f27d
feat(fetch): ingest changelog GitHub releases and RSS feeds
CrisSTEM Apr 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -350,6 +350,15 @@ Normalization notes for `v0.3.0`:
- `mode = "github_releases"` persists `content_items` as `release`
- `mode = "rss"` persists `content_items` as `changelog_entry`

#### Changelog runtime notes for `v0.3.0`
For the first live changelog runtime:

- `mode = "github_releases"` calls the GitHub releases API for each configured repository and normalizes non-draft releases into `content_items` with `item_type = "release"`
- `mode = "rss"` fetches the configured RSS feed URL and normalizes accepted RSS `<item>` entries into `content_items` with `item_type = "changelog_entry"`
- reruns rely on the shared `content_items` dedupe contract, so previously seen release or feed entries are not inserted again
- release-delta heuristics, Atom-specific handling, and non-GitHub changelog providers are intentionally deferred


### Deferred source-family validation

The current runtime already reserves `app_store_ios`, `app_store_android`, and `social` as source kinds, but their detailed binding-shape validation is intentionally deferred until those fetchers are implemented. The config contract therefore freezes the source kinds now without overclaiming runtime semantics that do not exist yet.
Expand Down
Loading
Loading