Skip to main content

releases

Raw release feed and review queue

📄️ Resolve a link request into the concrete `series.id` it targets, shared by the single-release [`link`] handler and the [`bulk_link`] action. The `posted_at` anchor is only consulted on the provider path, where it seeds the freshly-upserted series' first-seen timestamp; callers pass the release's own `posted_at` (single link) or the anchor release's (bulk). Bulk-link a set of review-queue releases to one series. The body's `ids` (intersected with the queue statuses) select the releases; the series is named exactly as in the single-release [`link`] handler. Each release is linked individually (clearing its candidates and bumping the series' highest volume/chapter marks) so the result matches what N single links would produce. The operator is responsible for the selection being one series' releases; the endpoint links them blindly to the chosen target.

Resolve a link request into the concrete `series.id` it targets, shared by

📄️ Re-run the resolver against every release currently visible in the review queue (`unresolved`, `ambiguous`, `review_pending`). With `?includeResolved=true`, also walks `resolved` rows (skipping manually-linked ones). Spawns a background task and returns immediately so the request doesn't block on what can be a multi- minute walk. A dedicated per-process lock prevents a second click from spawning a parallel walk; in that case the response is `{ triggered: false, skipped: true }`.

Re-run the resolver against every release currently visible in the