Releases

A few things from the current codebase that might save time on this:

Deep links already point at a releases URL
The inbox normalizes GitHub “release” notification API URLs to /{owner}/{repo}/releases (see RE_API_RELEASES and the getNotificationWebUrl branch in apps/dashboard/src/components/inbox/inbox-page.tsx). There is no matching route under apps/dashboard/src/routes/_protected/$owner/$repo/ yet, so implementing a releases page at that path would also make those inbox links work end-to-end.

Natural places to wire UI
Repo-scoped list flows today follow the file-route + TanStack Query pattern, e.g. apps/dashboard/src/routes/_protected/$owner/$repo/issues.index.tsx and .../pulls.tsx. The right-hand “activity” column on the repo overview is built in apps/dashboard/src/components/repo/repo-activity-cards.tsx (PRs, Issues, and optionally Discussions with a “view all” link), which is a close analogue if you want a GitHub-style entry point next to those.

Data layer
apps/dashboard/src/lib/github.query.ts defines query keys and *QueryOptions helpers for repo-scoped features; there is not yet a releases list helper or key. New work would likely add a small server function in github.functions.ts (Octokit’s REST repos releases endpoints) and mirror the pagination/staleTime patterns used for repo issues/pulls.

Related surface area
Release activity is already represented in the profile feed components (ReleaseEvent in user-activity-feed.tsx and handling in github.functions.ts), but that is display-only, not a full releases browser.

If you want per-release detail in-app later, you may also want a route that matches a single release (inbox only maps the list path today).