Skip to content

t2vi/arrgh](https:

v0.0.11 Breaking

This release includes 2 breaking changes for platform teams planning a safe upgrade.

Published 9d Media Servers
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Affected surfaces

auth breaking_upgrade

Summary

AI summary

Updates What's new, Other improvements, and Queue visibility and ownership across a mixed release.

Full changelog

*ARRgh v0.0.11 — MangaUpdates as Metadata Authority

Released: 2026-05-25


What's new

MangaUpdates replaces source fan-out for Discover

All metadata (titles, descriptions, covers, authors, year, tags) now comes from a single authoritative source: MangaUpdates (api.mangaupdates.com). No API key required.

  • Discover queries MangaUpdates directly — faster, consistent results across all titles.
  • Trending uses MangaUpdates latest-releases feed instead of aggregating per-source trending endpoints.
  • Source plugins are now download-only backends. The /search, /meta, /trending, and /cover plugin endpoints are no longer called by arrgh (existing plugins that implement them continue to work; those routes are simply ignored).
  • Add from Discover now takes a mangaupdates_id instead of source + source_id. After adding, source matching runs asynchronously in the background — arrgh searches each registered source for the title and registers source links when found.

Queue visibility and ownership (queue rearchitecture)

  • Download Queue is globally visible to all authenticated users (explicit content filtered per-user).
  • Members can cancel only their own queue items. Admins can cancel any.
  • Remove + delete files is now admin-only and requires confirmation.
  • Queue items carry a queued_by reference to the user who triggered them.

Manga detail fixes

  • "Remove + delete files" now visible to admins — was incorrectly gated behind downloaded > 0, hiding the button whenever chapter data hadn't loaded yet. Now always shown to admins.
  • File deletion is admin-only and requires confirmation — non-admins no longer see the option; admins are prompted with a window.confirm before files are deleted.
  • Dropdown no longer clipped by hero blur — the hero section's overflow-hidden was applied to the outer container, clipping the "Remove" dropdown menu. Moved overflow-hidden to a wrapper around only the blurred background layers so the dropdown renders above the hero correctly.

Bug fixes

  • MangaUpdates Trending 400 Bad RequestPOST /v1/releases/search was called with invalid orderby: "time" and include_metadata: "series" (must be boolean). Fixed: removed orderby, changed include_metadata to true, rewrote as two-step fetch (releases → unique series_ids → parallel GET /v1/series/{id}) since the releases metadata endpoint returns only minimal series info.

Other improvements

  • New manga.mangaupdates_id column links library titles to MangaUpdates records.
  • Covers downloaded directly from MangaUpdates CDN; no plugin proxy needed.
  • Source matching after Add: background task searches all registered sources by title, registers matching source links, syncs chapters.

New API endpoints

| Method | Path | Description |
|--------|------|-------------|
| GET | /api/discover | MangaUpdates title search (?q=) |
| GET | /api/discover/trending | MangaUpdates latest releases |
| POST | /api/discover/add | Add manga by mangaupdates_id |

Breaking change: POST /api/discover/add request body now takes mangaupdates_id instead of source + source_id + alternatives. Clients sending the old shape will receive a 422.


Upgrading

docker compose pull
docker compose up -d

Schema change — migration 0030_mangaupdates_id adds manga.mangaupdates_id TEXT with a unique index. Applied automatically on startup.

Existing library — titles added before v0.0.11 won't have a mangaupdates_id yet. A startup backfill is planned for v0.0.12 (high-confidence title matching runs automatically at boot). Until then, existing library titles continue to work; Discover's in-library check will not recognise them from search results.

Plugin updates — no plugin changes required. Existing plugins that implement /search or /trending continue to load; those endpoints are simply never called.

Breaking Changes

  • POST /api/discover/add now requires `mangaupdates_id` instead of `source + source_id + alternatives`; old payloads return 422.
  • Source plugin endpoints `/search`, `/meta`, `/trending`, and `/cover` are no longer invoked by arrgh (ignored but still loadable).

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track t2vi/arrgh](https:

Get notified when new releases ship.

Sign up free

About t2vi/arrgh](https:

All releases →

Related context

Earlier breaking changes

  • v0.1.13 Removes the single `/api/discover/trending` endpoint; clients must use lane‑specific endpoints.
  • v0.1.13 Removes `MangaFire` source entirely, including plugin and related code.
  • v0.1.2 Rust/Axum server removed; replaced with .NET 9 ASP.NET Core Minimal API implementation.
  • v.0.0.9 Drops manga.source and chapters.source_id columns from schema.

Beta — feedback welcome: [email protected]