![]() Install compatibility tool from nuget instead of pulling a github release.Clarify comment and log actual search string in TMDB search provider.Use the "legacy" AuthenticationException in AuthService.Bump SQLitePCLRaw.bundle_e_sqlite3 from 2.0.2 to 2.0.3.Add MessageId to websocket message, fix ws exception.Fix server error when user enters a password, but none is set.Remove warnings from MediaBrowser.LocalMetadata.Add newlines after closing braces (SA1513/SA1516).Fix for Many log messages from Media Renderers trying to see old events.Add full stop at end of comments (SA1629).Bump Swashbuckle.AspNetCore from 5.0.0 to 5.4.1.Bump CommandLineParser from 2.7.82 to 2.8.0.Bump sharpcompress from 0.25.0 to 0.25.1.Remove code for handling single hyphen arguments.Fix Task that ignores cancellation request.Remove (unused) SessionId route parameter.Enable TreatWarningsAsErrors in Release for MediaBrowser.Providers.gitignore: ignore jellyfin-web symlink &. Prevent system plugins from being uninstalled.Bump prometheus-net from 3.5.0 to 3.6.0.Bump Swashbuckle.AspNetCore from 5.4.1 to 5.5.0.Bump prometheus-net.AspNetCore from 3.5.0 to 3.6.0.Remove EasyPassword from Authentication providers.Revert ILoggerFactory usage in BaseItem.cs.catch skia errors when getting image dimensions.Use constructor to set optimal config values.Add support for ReadOnlySpan in IgnorePatterns.Bump AutoFixture from 4.11.0 to 4.12.0.Bump Swashbuckle.AspNetCore from 5.5.0 to 5.5.1.Respect FFMpeg path passed via Environment Variable.Use newer Jellyfin.XmlTv for Guide Fixes.Add FFmpeg 4.3 detection and solve the green line on QSV HWA.Fix TypeLoadException during plugin load.Add conditionals to root YAML definition.Make User Authentication Case-insensitive and remove EF Core Log spam.Keep playstate during syncplay group creation.Bump AutoFixture from 4.12.0 to 4.13.0.Prevent failure to bind to Auto Discover port being a fatal error.Explicitly add what Azure used to do implicitly.Only fetch Next Up for episodes that have been fully matched.TVDB: Fetch image keytypes before querying images.Fix QSV subtitle burn-in on windows and P010 detect.Catch HttpRequestException when requesting plugins.Bump the minimun required jellyfin-ffmpeg version.Add UserId filter to ActivityLog Entries endpoint.Remove profile image before setting new.If not, try running apt install jellyfin-server instead.~ Fixed by package version 10.6.0-2 of jellyfin-server and jellyfin. If your upgrade fails, immediately run apt -f install with no other options and this should correct the situation. ~The seamless apt upgrade seems to have been more troublesome than anticipated. This should be fine unless you wish to use QSV, which was buggy in v4.2.3 if you do, we recommend upgrading to a newer operating system version for your Jellyfin instance or switching to Docker-based installs in order to take full advantage of jellyfin-ffmpeg v4.3.1. Users of these releases will continue to use jellyfin-ffmpeg v4.2.3. The updated jellyfin-ffmpeg v4.3.1 was not built on the following older releases due to an build failure of an additional included amd64-only dependency. You should upgrade both at the same time for maximum compatibility, performance, and stabiity. This release features a simultaneous release of jellyfin-ffmpeg v4.3.1. Make a backup of your instance before upgrading so downgrades can be a smooth and simple process. UPON UPGRADING YOUR INSTANCE TO 10.6.0, YOU WILL NOT BE ABLE TO DOWNGRADE TO 10.5.5 OR EARLIER WITHOUT RENAMING AND EDITING MUTIPLE FILES IN MUTIPLE PLACES. This release introduces the first of several major database schema changes as we move to EF Core, specifically to the User and Activity databases. If it does become evident that this is a major issue, a fix will be prioritized for a 10.6.1 release. There are future plans to investigate and address this further in a general way, but the situation right now does not seem serious enough to block a stable release. The current consensus is that this is due to the garbage collection in C# not being agressive enough. We have had several, but not many, reports of high memory usage in unstable 10.6.0 builds, most often caused by frequent library scanning. Memory usage may be higher in 10.6.0 compared to previous versions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |