From 4fc79f39f7594a6ce2eb3c2445a9e0fb66d43e91 Mon Sep 17 00:00:00 2001
From: Duncan Tourolle <duncan@tourolle.paris>
Date: Sat, 27 Jun 2026 11:23:53 +0200
Subject: [PATCH] Fix CI

---
 Jellyfin.Plugin.SRFPlay/Jellyfin.Plugin.SRFPlay.csproj | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/Jellyfin.Plugin.SRFPlay/Jellyfin.Plugin.SRFPlay.csproj b/Jellyfin.Plugin.SRFPlay/Jellyfin.Plugin.SRFPlay.csproj
index c824c13..3cd9803 100644
--- a/Jellyfin.Plugin.SRFPlay/Jellyfin.Plugin.SRFPlay.csproj
+++ b/Jellyfin.Plugin.SRFPlay/Jellyfin.Plugin.SRFPlay.csproj
@@ -8,6 +8,15 @@
     <Nullable>enable</Nullable>
     <AnalysisMode>AllEnabledByDefault</AnalysisMode>
     <CodeAnalysisRuleSet>../jellyfin.ruleset</CodeAnalysisRuleSet>
+    <!--
+      Pin AssemblyVersion/FileVersion to a valid major.minor.build.revision form. The Jellyfin
+      meta build workflow injects a date-based package version (e.g. 1.0.20260627.179) whose
+      build segment exceeds the 16-bit limit (0-65535) that AssemblyVersion/FileVersion require,
+      which otherwise fails the compile (CS7034/CS7035). The injected -p:Version still applies to
+      the package/plugin manifest; only the .NET assembly identity is pinned here.
+    -->
+    <AssemblyVersion>1.0.0.0</AssemblyVersion>
+    <FileVersion>1.0.0.0</FileVersion>
   </PropertyGroup>
 
   <ItemGroup>