chore: Release 6.2.0 (#186)

Co-authored-by: github-actions[bot] <noreply@onesignal.com>
Co-authored-by: Fadi George <fadii925@gmail.com>

Author: 3 people

.github/workflows/e2e.yml

@@ -96,12 +96,9 @@ jobs:
       github.event_name == 'push' ||
       github.event.inputs.platform == 'ios' ||
       github.event.inputs.platform == 'both'
-    # macOS 15 runners only ship up to Xcode 26.3, but the .NET 10 iOS
-    # workload set 10.0.300+ pulls Microsoft.iOS.Sdk.net10.0_26.4 which
-    # requires Xcode 26.4 ("This version of .NET for iOS (26.4.x) requires
-    # Xcode 26.4"). macos-26 ships Xcode 26.4.1 as the default, so we pin
-    # to it explicitly until macos-latest migrates (scheduled for June 15,
-    # 2026 per the GitHub Actions changelog).
+    # The .NET 10 iOS workload currently pulls Microsoft.iOS.Sdk.net10.0_26.5,
+    # which rejects newer Xcode releases. Pin Xcode so setup-xcode does not
+    # select latest-stable after the runner image advances.
     runs-on: macos-26
     steps:
       - name: Checkout
@@ -112,14 +109,10 @@ jobs:
         with:
           dotnet-version: '10.0.x'
 
-      # latest-stable resolves to the newest non-prerelease Xcode on the
-      # runner (26.4.1 on macos-26 today), which keeps us in sync with
-      # whatever the .NET iOS workload requires without hardcoding a
-      # version that may roll forward.
       - name: Select Xcode
         uses: maxim-lobanov/setup-xcode@v1
         with:
-          xcode-version: latest-stable
+          xcode-version: '26.5'
 
       # Both workloads are required even though only the iOS TFM is built,
       # because NuGet restore walks every declared TargetFramework of the

OneSignalSDK.DotNet.nuspec

@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="utf-8"?>
 <package xmlns="http://schemas.microsoft.com/packaging/2012/06/nuspec.xsd">
     <metadata>
-        <version>6.1.11</version>
+        <version>6.2.0</version>
         <id>OneSignalSDK.DotNet</id>
         <title>OneSignal SDK for .NET and MAUI</title>
         <authors>OneSignal</authors>