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

Update fallenbagel/jellyseerr Docker tag to v2 #393

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 19, 2024

This PR contains the following updates:

Package Update Change
fallenbagel/jellyseerr major 1.7.0 -> 2.1.0

Release Notes

Fallenbagel/jellyseerr (fallenbagel/jellyseerr)

v2.1.0

Compare Source

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

v1.9.2

Compare Source

[!WARNING]

Warning (For windows users)

Before you yarn build please downgrade your typeorm version by yarn add [email protected]
typeorm/typeorm#9860 (comment)

Bug Fixes

This release is also available on:

  • v1.9.2

v1.9.1

Compare Source

Bug Fixes

v1.9.0

Compare Source

Features

v1.8.1

Compare Source

Reverts
  • Revert "fix: disable seasonfolder option in sonarr for jellyfin/Emby users" (#​718) (cd0fa3e), closes #​718

This release is also available on:

  • v1.8.1

v1.8.0

Compare Source

Features

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), 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 was generated by Mend Renovate. View the repository job log.

@github-actions github-actions bot added the area/cluster Changes made in the cluster directory label Oct 19, 2024
@renovate renovate bot force-pushed the renovate/fallenbagel-jellyseerr-2.x branch from eba098a to 558daa7 Compare November 13, 2024 01:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cluster Changes made in the cluster directory renovate/container type/major
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants