Skip to content

Releases: Viperinius/jellyfin-plugin-spotify-import

1.17.3.0

08 Jun 19:17

Choose a tag to compare

Fixed

  • Fix skipped import run if only Spotify-owned playlists are configured (see #86)

1.17.2.0

02 Jun 18:00

Choose a tag to compare

Changed

  • use item field of a playlist track if the track field is not set (API parsing)

1.17.1.0

27 May 20:59

Choose a tag to compare

Fixed

  • Update Jellyfin SDK to work with version 10.11.10

1.17.0.0

24 Feb 22:58

Choose a tag to compare

Changed

  • Rework API interactions to work with the latest Spotify API changes (see #79)

1.16.0.0

21 Oct 18:06

Choose a tag to compare

Added

  • Support for Jellyfin 10.11

Caution

As described by the Finamp team here, Jellyfin 10.11 might still have a few kinks in regards to music libraries. While I haven't seen noticable problems for this plugin, you might want to be cautious when upgrading to 10.11.

If you want to stay on 10.10 for now, you won't miss any features from this plugin release as it only creates compatibility with 10.11.

1.15.1.0

21 Oct 17:37

Choose a tag to compare

Changed

  • Replace the default URL for Spotify TOTP

1.15.0.0

01 Oct 20:03

Choose a tag to compare

Added

  • Also ignore diacritics when using match level Ignore Punctuation + Case (or further relaxed levels)

Changed

  • Manual map interface now allows pasting in JSON (e.g. missing tracks file entries)
  • Manual map entries can now be specified either be the previously used information or just using the Spotify track ID / URI (similar to how playlist URIs are handled when configuring the plugin)

1.14.1.0

13 Sep 13:30

Choose a tag to compare

Fixed

  • Excessive memory use when updating the ISRC / MusicBrainz cache in some situations

1.14.0.0

12 Sep 17:20

Choose a tag to compare

Added

  • New optional matching method via MusicBrainz and ISRC IDs (see the README for more details)
  • The plugin settings page now contains a checkbox to activate the new MusicBrainz matching method
  • Support for the import of the "Liked Songs" section from Spotify (see the README for more details)

Note

If you've used this plugin prior to version 1.14.0.0 and want to import your liked songs, you need to re-authorise in the plugin settings. Otherwise you will see an error in your logs if you try to import them. This happens because the authentication token created by previous versions did not request the right to read the Spotify user library yet.

Changed

  • The current scopes of the Spotify auth token are now displayed on the plugin settings page (this can be used to check whether you need to recreate said token before being able to import "Liked Songs")

1.13.1.0

14 Aug 16:46

Choose a tag to compare

Fixed

  • Fix missing progress reporting of import task
  • Fix wrong parameters for some logging entries (see issue #63)
  • Fix procedure to aquire auth token for alternative Spotify provider after recent changes made by Spotify (again)