avm/hassio-addons
1
0
Fork 0
mirror of https://github.com/alexbelgium/hassio-addons.git synced 2026-09-06 09:53:33 +02:00
Code Issues Packages Projects Releases Wiki Activity
Files
docs/skill-simplify-after-review
hassio-addons/seerr/CHANGELOG.md
Alexandre 29ce08c162 fix(seerr): reapply the asset cache-bust reverted by the builder (#2975) (#2997) 
Restores #2993 verbatim. It was merged, then reverted by the builder's
revert-on-failure job a minute later - not because of anything in it, but
because EndBug/add-and-commit's floating v11 tag had moved to a release whose
action.yml no longer loads, so prebuild-sanitize failed before running a step.
The tag is pinned back to v11.0.0 in #2996, which has to land first for the
builder to get past that job.

The change itself is unchanged and still verified against the real njs module:
the rewritten /_next paths carry the add-on version, njs strips the marker
before proxying, so a browser holding the year-cached rewritten bundle fetches
fresh URLs on the first load after the update.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
2026-08-19 07:30:20 +02:00

4.5 KiB
Raw Permalink Blame History

3.4.1.3 (2026-08-18)

  • Fixed the 404: Not Found on Discover persisting for browsers that had already opened Seerr through ingress, even after 3.4.1.1 and 3.4.1.2 were installed (#2975). Seerr serves its JavaScript bundle with Cache-Control: public, max-age=31536000, immutable, and the add-on's nginx rewrites that bundle to carry the ingress prefix - which strips the ETag and Last-Modified a browser would revalidate with. Since every add-on version served the same upstream build, the chunk URLs never changed either, so a browser kept replaying the broken 3.4.1/3.4.1.1 JavaScript from its own cache for up to a year and no fix could reach it. That is why the report persisted on the origin the reporter uses daily (https://<domain>/) while a browser that had never cached it (http://<ip>:8123/) already showed the fixed behaviour. The asset paths now carry the add-on version, so each release has its own URLs and the first page load after an update fetches the current bundle. Only ingress was affected; the directly published port 5055 always worked.

3.4.1.2 (2026-08-18)

  • Fixed Discover in the sidebar still failing through ingress after 3.4.1.1 (#2975). The trailing slash added in 3.4.1.1 was also applied to the copy of the link inside Seerr's JavaScript bundle, and Next.js' client-side router strips a trailing slash before navigating: it then sent the click to a URL Home Assistant does not route, so it either landed on the same 404: Not Found or threw Invariant: attempted to hard navigate to the same URL and did nothing at all. The bundle is no longer rewritten, so Discover routes inside the app exactly like Requests, Issues and Settings already did. The server-rendered link keeps its trailing slash. Only ingress was affected; the directly published port 5055 always worked.

3.4.1.1 (2026-08-16)

  • Fixed 404: Not Found when clicking Discover in the sidebar through ingress (#2975). Seerr's Discover link points at /, which nginx rewrote to the ingress entry without a trailing slash; Home Assistant only routes ingress on /api/hassio_ingress/<token>/…, so the request was rejected by Home Assistant before reaching the add-on. Only ingress was affected; the directly published port 5055 always worked.

3.4.1 (2026-08-01)

3.3.0.1 (2026-07-28)

  • Fixed searches failing through ingress with 500 Internal Server Error (#2906, #2646). Home Assistant's ingress proxy re-encodes the query string and passes a space as +, along with a bare : / ? @ ! $ ' ( ) * , - all of which Seerr's OpenAPI validator rejects as reserved characters. Nginx now re-encodes them before proxying, so titles such as Monsters, Inc., Ocean's Eleven, Mission: Impossible and Who? What? search correctly. Only ingress was affected; the directly published port 5055 always worked.

3.3.0 (2026-06-05)

3.2.0 (2026-04-23)

3.2.0 (21-04-2026)

  • Minor bugs fixed

3.1.0-4 (14-04-2026)

  • Minor bugs fixed

3.1.0-3 (14-04-2026)

  • Minor bugs fixed

3.1.0-2 (22-03-2026)

  • Added configurable NODE_MEMORY_LIMIT option (default 512 MB) to control Node.js heap size and prevent OOM kills

3.1.0 (22-03-2026)

3.0.1 (2026-02-21)

3.0.1-6 (20-02-2026)

  • Minor bugs fixed

3.0.1-5 (19-02-2026)

  • Minor bugs fixed

3.0.1-4 (19-02-2026)

  • Minor bugs fixed

3.0.1-3 (19-02-2026)

  • Minor bugs fixed

3.0.1-2 (19-02-2026)

  • Added Home Assistant Ingress support for Seerr with an internal NGINX reverse proxy and ingress-aware response rewriting.
  • Enabled ingress in the add-on manifest and updated startup flow to launch NGINX before Seerr.

v3.0.1 (2026-02-17)

  • Initial release based on the Overseerr add-on, updated to the Seerr upstream image and naming.
  • Switched base image to seerr/seerr:latest and updated metadata/options for the new slug.
  • Remove bundled binary image assets from the add-on directory as requested by review feedback.