Skip to content

t2vi/arrgh](https:

v0.1.5 Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

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

✓ No known CVEs patched in this version

Affected surfaces

breaking_upgrade

ReleasePort's take

Light signal
editorial:auto 2d

Remote deployments now succeed without a 403 error after removing the host‑side web assets volume. The CI pipeline was corrected to use port 8282.

Why it matters: Fixes deployment failures (severity 40) and aligns CI tests with the updated service port, ensuring reliable builds.

Summary

AI summary

Remote deployments no longer return 403 after removing the host‑side web assets volume and fixing a CI port mismatch.

Changes in this release

Bugfix High

Server no longer crashes on startup when upgrading from pre-migration databases.

Server no longer crashes on startup when upgrading from pre-migration databases.

Source: llm_adapter@2026-06-01

Confidence: high

Bugfix Medium

Remote deployments no longer return 403; web UI served from baked image.

Remote deployments no longer return 403; web UI served from baked image.

Source: llm_adapter@2026-06-01

Confidence: high

Bugfix Medium

CI API test layer updated to use port 8282 instead of 8080.

CI API test layer updated to use port 8282 instead of 8080.

Source: llm_adapter@2026-06-01

Confidence: high

Full changelog

*ARRgh v0.1.5 — Portainer / remote deployment fix

Released: 2026-06-01


Highlights

  • Portainer fix — remote deployments (Portainer, Docker Swarm, docker compose pull) no longer return 403. Web UI now served from the baked image; no host-side web/dist directory required.
  • CI port fix — API test layer in CI was pointing at the old port 8080; updated to 8282.
  • Migration bootstrap — server no longer crashes on startup when upgrading from a pre-migration database (table "external_sources" already exists). Also repairs partial-schema databases (old Rust builds missing default_explicit / is_community / source_key columns) that caused 500 errors on source PATCH/save.

What's new

Migration bootstrap for existing databases

Upgrading from an older arrgh installation (including the original Rust server) failed at startup with:

SQLite Error 1: 'table "external_sources" already exists'

This happened because EF Core's Migrate() tried to apply InitialSchema against a database that already had all the tables, but had no __EFMigrationsHistory table to indicate that.

Fix: MigrationBootstrap.Bootstrap() now runs before Migrate(). It detects a pre-migration database (tables present, no history table), repairs the schema (creates missing tables, patches missing columns in external_sources), and inserts the appropriate migration records so Migrate() only applies genuinely new migrations. Idempotent — no effect on fresh or already-migrated databases.

Web assets served from image

The docker-compose.yml previously included:

volumes:
  - ./web/dist:/var/www/arrgh:ro

On remote hosts (Portainer, bare docker compose pull) this directory doesn't exist, causing nginx to serve an empty root → 403 Forbidden.

The web UI is built into the Docker image at /var/www/arrgh by the Dockerfile. The bind mount is only useful locally (avoids rebuilding the image after a frontend change).

Fix: bind mount removed from docker-compose.yml. Moved to docker-compose.override.yml which Docker Compose applies automatically for local docker compose up.

Local dev — no change needed. docker-compose.override.yml is picked up automatically.

Remote / Portainer — pull the new image and redeploy. No volume or config changes needed.

CI API test port

e2e.yml hardcoded BASE_URL: http://localhost:8080 — predated the port change to 8282. Updated to http://localhost:8282.


Upgrading

docker compose pull
docker compose up -d

If you previously added - ./web/dist:/var/www/arrgh:ro to your own docker-compose.yml or Portainer stack, remove it.

Breaking Changes

  • Removed volume `- ./web/dist:/var/www/arrgh:ro` from `docker-compose.yml`; remote deployments must no longer provide this host directory.

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]