Update Policy

This document describes how idgard Sync tracks and adopts updates to its core dependencies.

Component	Strategy	Lag after support/release end
Windows OS (feature update)	Raise minimum after MS support ends	3 – 6 months
Windows App SDK (major version)	Stay on latest major ≥ 6 months old	≥ 6 months
.NET Desktop Runtime (major/LTS)	Adopt LTS versions only	6 – 12 months after GA
.NET Desktop Runtime (patch)	Always use latest patch of current LTS	Immediate

Windows Operating System

We follow Microsoft's servicing timeline for Windows feature updates.

Rule: We raise the minimum supported Windows version 3 to 6 months after Microsoft ends mainstream support for the version currently listed as the minimum. The exact timing within that window depends on release readiness and testing.

Resource	Link
Windows 10 release information	learn.microsoft.com – Windows 10
Windows 11 release information	learn.microsoft.com – Windows 11

Windows App SDK

Rule: We target the latest major version that is at least 6 months old at the time of a release. We do not adopt a brand-new major version immediately; we wait until it has been available for at least 6 months before making it the required minimum. Within the chosen major version we always ship the latest available release.

Resource	Link
Windows App SDK downloads & release notes	learn.microsoft.com – Windows App SDK

.NET Desktop Runtime

Rule: We target Long-Term Support (LTS) releases only (e.g., .NET 10, .NET 12). A new LTS version is adopted 6 to 12 months after its GA release, once the ecosystem has stabilized. Within the adopted major version we always ship the latest minor or patch release (e.g., 10.0 today).

Non-LTS / Standard-Term Support (STS) releases are not used as the required runtime.

Resource	Link
.NET download page & release schedule	dotnet.microsoft.com