From da5db5bf118bd2920b70ac9ce790a5bd17a1e2df Mon Sep 17 00:00:00 2001
From: Richard Markiewicz <rmarkiewicz@devolutions.net>
Date: Thu, 4 Dec 2025 10:11:34 -0500
Subject: [PATCH] chore(release): prepare for Devolutions.IronRdp v2025.12.4.0
 (#1048)

We still don't have a means to set the nuget version directly in the
workflow. I thought of adding it, but on closer inspection we have logic
to handle package and product version differently (and the same is true
of sspi-rs etc) and probably needs a closer look. It can be troublesome
to deploy a newer nuget package that doesn't increment the assembly
versions (for example - and it shouldn't be an issue for Devolutions,
but maybe for other consumers - Windows Installers generally might not
overwrite a DLL if the version number is not newer than what is already
installed.

For now, I just bump the package version manually.
---
 ffi/dotnet/Devolutions.IronRdp/Devolutions.IronRdp.csproj | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ffi/dotnet/Devolutions.IronRdp/Devolutions.IronRdp.csproj b/ffi/dotnet/Devolutions.IronRdp/Devolutions.IronRdp.csproj
index 5ae81afe..38fc2e65 100644
--- a/ffi/dotnet/Devolutions.IronRdp/Devolutions.IronRdp.csproj
+++ b/ffi/dotnet/Devolutions.IronRdp/Devolutions.IronRdp.csproj
@@ -4,7 +4,7 @@
     <Company>Devolutions</Company>
     <Description>Bindings to Rust IronRDP native library</Description>
     <LangVersion>latest</LangVersion>
-    <Version>2025.9.24.0</Version>
+    <Version>2025.12.4.0</Version>
     <ImplicitUsings>enable</ImplicitUsings> <!-- FIXME: set to disable -->
     <Nullable>enable</Nullable>
     <AllowUnsafeBlocks>true</AllowUnsafeBlocks>