From c4285c8e13d39c04301ad66b3300b6357b68a316 Mon Sep 17 00:00:00 2001
From: Ivan Vydrin <ivan.vydrin@techfabric.com>
Date: Thu, 30 Jul 2026 20:01:39 +0300
Subject: [PATCH] Stop the meta-package packing an empty symbol package

The 4.1.0 publish pushed fifteen packages and then failed: nuget.org
returns 400 for a symbol package containing no .pdb files, and the
meta-package has no assembly to produce one. The repository packs symbols
for everything by default, so this project has to opt out by name.

The failure landed after real packages had already gone up, and the tag
and GitHub Release steps run after publishing, so the run left nuget.org
half-updated with no tag to show for it. Pushing is idempotent
(--skip-duplicate), so re-running completes it.
---
 src/Healthie.NET.Package/Healthie.NET.Package.csproj | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/src/Healthie.NET.Package/Healthie.NET.Package.csproj b/src/Healthie.NET.Package/Healthie.NET.Package.csproj
index eb82af1..03ddd23 100644
--- a/src/Healthie.NET.Package/Healthie.NET.Package.csproj
+++ b/src/Healthie.NET.Package/Healthie.NET.Package.csproj
@@ -21,6 +21,13 @@
     <EnablePackageValidation>false</EnablePackageValidation>
     <GenerateDocumentationFile>false</GenerateDocumentationFile>
     <NoWarn>$(NoWarn);NU5128</NoWarn>
+
+    <!--
+      No assembly means no .pdb, and nuget.org rejects a symbol package containing none of them
+      with a 400. The repository packs symbols for everything by default, so this has to opt out
+      explicitly or the push fails after the real packages have already gone up.
+    -->
+    <IncludeSymbols>false</IncludeSymbols>
   </PropertyGroup>
 
   <ItemGroup>