t2vi/arrgh](https:

v0.1.7 Feature

This release adds 3 notable features for engineering teams evaluating rollout.

Published 16h Media Servers

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Summary

AI summary

Updates What's new, Highlights, and ongoing/completed/hiatus/cancelled across a mixed release.

Changes in this release

Type	Severity	Summary	CVE
Feature
Feature	Medium	Adds sort options (recent, title A‑Z/Z‑A, year) to GET /api/titles Adds sort options (recent, title A‑Z/Z‑A, year) to GET /api/titles Source: llm_adapter@2026-06-03 Confidence: high	—
Feature	Medium	Adds content_type and status filter parameters to GET /api/titles Adds content_type and status filter parameters to GET /api/titles Source: llm_adapter@2026-06-03 Confidence: high	—
Feature	Medium	UI shows active filter count badge on the Filters button UI shows active filter count badge on the Filters button Source: llm_adapter@2026-06-03 Confidence: high	—
Feature	Low	Adds collapsible filter panel in Library UI Adds collapsible filter panel in Library UI Source: llm_adapter@2026-06-03 Confidence: high	—
Bugfix	Medium	Fixes nhentai prefix upgrade to match word‑boundary prefixes for manga titles Fixes nhentai prefix upgrade to match word‑boundary prefixes for manga titles Source: llm_adapter@2026-06-03 Confidence: high	—
Bugfix	Medium	Prevents misclassification of manhwa/novel titles as hentai during nhentai upgrade Prevents misclassification of manhwa/novel titles as hentai during nhentai upgrade Source: llm_adapter@2026-06-03 Confidence: high	—

Full changelog

*ARRgh v0.1.7 — Library sort & filter, hentai classification fixes

Released: 2026-06-03

Highlights

Library sort & filter — sort by recently added, title A–Z/Z–A, or year; filter by content type (manga/manhwa/manhua/novel) and status (ongoing/completed/hiatus/cancelled); active filter count badge on the Filters button
nhentai prefix upgrade — nhentai's short search titles (e.g. "kayanetori") now correctly upgrade MangaUpdates manga results with the full title ("KayaNetori Kaya-Nee Series Aizou Ban") to content_type=hentai using word-boundary prefix matching
Manhwa/novel protection — nhentai upgrade is now restricted to content_type=manga only; explicit manhwa/manhua/novel titles that happen to share a name with an nhentai doujin are no longer misclassified as hentai

What's new

Library sort & filter

GET /api/titles now accepts:

sort — recent (default), title_asc, title_desc, year
content_type — comma-separated list (e.g. manga,manhwa)
status — comma-separated list (e.g. ongoing,completed)

The library UI exposes a sort dropdown and a collapsible filter panel. Active filter count shown as a badge on the Filters button.

nhentai prefix upgrade (word-boundary)

MergeFanOut previously required exact normalized title match to upgrade a MU manga result to hentai. nhentai search often returns short/abbreviated titles, causing the upgrade to miss. The logic now also matches when the nhentai normalized title is a word-boundary prefix of the MU normalized title (muNorm.StartsWith(nhentaiNorm + " ")).

Manhwa/novel protection from nhentai upgrade

The upgrade guard now additionally requires ContentType == "manga". Explicit manhwa titles (e.g. "Moby Dick" by Yansae) that share a name with an nhentai doujin are no longer reclassified as hentai.

New API parameters

| Endpoint | New params |
|---|---|
| GET /api/titles | sort, content_type, status |

Upgrading

docker compose pull
docker compose up -d

No database migrations required.

View diff on GitHub

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

Share on X Share on Bluesky

Track t2vi/arrgh](https:

Get notified when new releases ship.

About t2vi/arrgh](https:

All releases →

Related context

Related tools

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.