Alerts and feeds
This page covers the three ways release news is pushed to you — weekly email alerts, the public RSS feed, and your personal stack RSS — and how to set them up.
Weekly email alerts
A summary email arrives only when your stack (the projects you follow) has changes that need action. What counts as "action needed" is defined in Understanding the data.
Prerequisites
- An account (GitHub or Google sign-in).
Setup
- Register projects in your stack at /settings.
- Turn alerts on from the same page. They are off by default, with separate toggles for breaking and security alerts.
- Email language follows your account's language setting (English if unset).
Delivery rules
- Send time: every Sunday at 10:00 UTC.
- Window: releases published during the previous UTC calendar week (Sunday through Saturday).
- No email on weeks with no action items.
Public RSS
Follow the full release stream in your reader. No account needed.
https://ratatosk.io/feed.xml
| Parameter | Values | Description |
|---|---|---|
lang |
en ko ja |
Summary language (default en) |
limit |
1–200 | Number of items (default 50; out of range is silently clamped) |
Entries include the complete summary, so you can read everything without
leaving your reader. Most readers find the feed from ratatosk.io alone;
if yours doesn't, paste the URL above directly.
Personal stack RSS
A feed of your own, carrying only your stack's releases.
- Issue a feed token at /settings.
- Add the issued URL to your reader:
https://ratatosk.io/feed.xml?token=<your token>
langandlimitwork exactly as on the public feed.- The
typefilter is available only on personal feeds:type=security— only releases with security action itemstype=breaking— only releases with compatibility-breaking action items- Both types are defined by the same "action needed" criteria in Understanding the data.
- The token can be reissued at any time in /settings (invalidating the old one). Treat the URL like a password — anyone who knows it can see what is in your stack.
Troubleshooting
No email arriving — check in order:
- Does your stack at /settings have projects registered? An empty stack has nothing to send.
- Is the alert toggle on? Alerts are off by default; forgetting to turn them on after registering a stack is the most common cause.
- Were there actually action items last week? Check your stack projects' recent releases at /releases. No email on a quiet week is normal.
Personal feed returns 401: the token was reissued and the old one invalidated. Copy the current URL from /settings again.
Personal feed is empty: an empty stack produces an empty feed by design. Register projects in your stack.
Next steps
- How action items are decided: Understanding the data
- The same data, programmatically: REST API