Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(container)!: Update image docker.io/fallenbagel/jellyseerr to v2 #1047

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

spicerabot[bot]
Copy link
Contributor

@spicerabot spicerabot bot commented Oct 15, 2024

This PR contains the following updates:

Package Update Change
docker.io/fallenbagel/jellyseerr major 1.9.2 -> 2.1.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

Fallenbagel/jellyseerr (docker.io/fallenbagel/jellyseerr)

v2.1.0

Compare Source

[!IMPORTANT]

Notice for build from source users

After running git pull to update your instance, please delete the dist, .next, and node_modules directories. Make sure to follow the proper steps, starting with Step 3: "Install Dependencies".

Highlights

image

  • New Proxy Settings: Support for configuring HTTP proxy settings from Settings > General. You can now set up a proxy for outgoing requests and have the ability to bypass local addresses.

  • Performance Degradation / Lag Fix: This release addresses an issue that particularly affected users with weaker hardware (e.g., Synology devices). Jellyseerr previously experienced significant lag (up to 10-15 seconds) when navigating to core pages that did not rely on external APIs, such as settings. The problem was caused by multiple requests to the blacklist modal for each series/movie card, which overloaded both the server and the browser, causing timeouts. This issue also impacted smooth scrolling, resulting in hangs when scrolling too quickly. The fix improves performance and resolves these issues.

Bug Fixes
Features

This release is also available on:

  • v2.1.0

v2.0.1

Compare Source

[!WARNING]

Warning (For linux/armv7 users)

Unfortunately we had to drop support for armv7 as Next.js 14 does not bundle @​next/swc support for armv7. We apologize for this, however, until they add support for it, there is nothing we can really do as we needed to upgrade to Next.js 14. On devices that support aarch64, we recommend using aarch64 (RPi3, RPi3B, RPi4+, etc).

Highlights

This release lays the groundwork for future feature integrations by resolving existing issues and should improve overall stability.

New setup page

The setup process has been improved. Emby users can now configure Jellyseerr without having to edit environment variable.

image

Blacklist media from Jellyseerr

Users with special permissions can blacklist media to hide it from users. The blacklist is managed in a new page with options to remove items.

image

Faster downloads update

Sync delay between Jellyseerr and the *arrs is now reduced. A request to Sonarr/Radarr is now made to refresh the monitored downloads right before retrieving the estimated download times.

Switch to Jellyfin API Tokens

Before, Jellyseerr used admin user auth tokens to connect to Jellyfin and perform requests. Now, it will switch to using API tokens instead, with these tokens being automatically generated from the previous auth tokens to ensure a seamless migration.

Details

Bug Fixes

This release is also available on:

  • v2.0.1

v2.0.0

Compare Source

[!WARNING]

Warning (For linux/armv7 users)

Unfortunately we had to drop support for armv7 as Next.js 14 does not bundle @​next/swc support for armv7. We apologize for this, however, until they add support for it, there is nothing we can really do as we needed to upgrade to Next.js 14. On devices that support aarch64, we recommend using aarch64 (RPi3, RPi3B, RPi4+, etc).

Highlights

This release lays the groundwork for future feature integrations by resolving existing issues and should improve overall stability.

New setup page

The setup process has been improved. Emby users can now configure Jellyseerr without having to edit environment variable. Existing users should have their JELLYFIN_TYPE=emby variable migrated to a setting in settings.json where mediaServerType=3.

image

Blacklist media from Jellyseerr

Users with special permissions can blacklist media to hide it from users. The blacklist is managed in a new page with options to remove items.

298769756-bdacaed7-85b8-4897-af9e-9ab6336c14bf

Faster downloads update

Sync delay between Jellyseerr and the *arrs is now reduced. A request to Sonarr/Radarr is now made to refresh the monitored downloads right before retrieving the estimated download times.

Switch to Jellyfin API Tokens

Before, Jellyseerr used admin user auth tokens to connect to Jellyfin and perform requests. Now, it will switch to using API tokens instead, with these tokens being automatically generated from the previous auth tokens to ensure a seamless migration.

Details

Bug Fixes
Code Refactoring
  • jellyfin: abstract jellyfin hostname, updated ui to reflect it, better validation (#​773) (38ad875)
Features
Reverts
BREAKING CHANGES
  • Deprecated the JELLYFIN_TYPE variable to identify Emby media server and
    instead rely on the mediaServerType that is set in the settings.json. Existing environment
    variable users can log out and log back in to set the mediaServerType to 3 (Emby).

  • Added a serverType to the /auth/jellyfin which requires a serverType to be
    set (jellyfin/emby)

  • refactor(auth): jellyfin/emby authentication to set MediaServerType

  • jellyfin: Jellyfin settings now does not include a hostname. Instead it abstracted it to ip,
    port, useSsl, and urlBase. However, migration of old settings to new settings should work
    automatically.


This release is also available on:

  • v2.0.0

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@spicerabot
Copy link
Contributor Author

spicerabot bot commented Oct 15, 2024

--- kubernetes/apps/media/jellyseer/app Kustomization: flux-system/jellyseer HelmRelease: media/jellyseer

+++ kubernetes/apps/media/jellyseer/app Kustomization: flux-system/jellyseer HelmRelease: media/jellyseer

@@ -29,13 +29,13 @@

             env:
               LOG_LEVEL: info
               PORT: 8080
               TZ: null
             image:
               repository: docker.io/fallenbagel/jellyseerr
-              tag: 1.9.2
+              tag: 2.1.0
             resources:
               limits:
                 memory: 512M
               requests:
                 cpu: 15m
                 memory: 128M

@spicerabot
Copy link
Contributor Author

spicerabot bot commented Oct 15, 2024

--- HelmRelease: media/jellyseer Deployment: media/jellyseer

+++ HelmRelease: media/jellyseer Deployment: media/jellyseer

@@ -42,13 +42,13 @@

         - name: LOG_LEVEL
           value: info
         - name: PORT
           value: '8080'
         - name: TZ
           value: null
-        image: docker.io/fallenbagel/jellyseerr:1.9.2
+        image: docker.io/fallenbagel/jellyseerr:2.1.0
         name: app
         resources:
           limits:
             memory: 512M
           requests:
             cpu: 15m

@spicerabot spicerabot bot force-pushed the renovate/docker.io-fallenbagel-jellyseerr-2.x branch from 3886dc9 to 86b5c14 Compare October 17, 2024 15:07
@spicerabot spicerabot bot force-pushed the renovate/docker.io-fallenbagel-jellyseerr-2.x branch from 86b5c14 to 032415e Compare November 12, 2024 06:11
@spicerabot spicerabot bot force-pushed the renovate/docker.io-fallenbagel-jellyseerr-2.x branch from 032415e to 69922f8 Compare November 12, 2024 23:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant