Set version to 0.1.0
🚀 Release Plugin / build-and-release (push) Successful in 1m43s

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-09-19 12:30:50 +02:00
co-authored by Claude Opus 5
parent 27cd2a3d37
commit 5120e7abba
2 changed files with 9 additions and 7 deletions
+3 -3
View File
@@ -1,7 +1,7 @@
<Project>
<PropertyGroup>
<Version>0.0.6.0</Version>
<AssemblyVersion>0.0.6.0</AssemblyVersion>
<FileVersion>0.0.6.0</FileVersion>
<Version>0.1.0.0</Version>
<AssemblyVersion>0.1.0.0</AssemblyVersion>
<FileVersion>0.1.0.0</FileVersion>
</PropertyGroup>
</Project>
+6 -4
View File
@@ -1,7 +1,7 @@
---
name: "Watched Together"
guid: "aa3288a0-e8c1-43e2-8045-8c3411142a5b"
version: "0.0.6.0"
version: "0.1.0.0"
# The plugin ships one package per Jellyfin generation. These defaults describe the 10.11 package;
# scripts/package.sh stamps targetAbi/framework for whichever generation it is asked to build.
targetAbi: "10.11.0.0"
@@ -28,6 +28,8 @@ dotnet_framework: "net9.0"
# Point at the plugin project rather than the solution so the test project is not packaged.
project: "Jellyfin.Plugin.WatchedTogether/Jellyfin.Plugin.WatchedTogether.csproj"
changelog: >
Adds support for Jellyfin 12 alongside 10.11. Each release now ships two packages:
one built against 10.11 on .NET 9 and one against 12 on .NET 10, and the plugin
repository serves whichever matches your server.
Shared accounts now inherit their members' parental restrictions, strictest wins:
rating cap, unrated-item block, blocked and allowed tags. A per-group slider on the
plugin page raises the rating cap anywhere up to the loosest member's; members stricter
than the chosen cap can then no longer unlock the account with their password. Existing
shared accounts are tightened to their strictest member on first start after upgrading.