From 57cf7842342b065d5feaf0a35000c81e7c85cf17 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Thu, 2 Oct 2025 16:26:50 +0000 Subject: [PATCH 1/2] Initial plan From 4b4275e38452e8194184c57d64239043bf1c1a21 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Thu, 2 Oct 2025 16:29:51 +0000 Subject: [PATCH 2/2] Add NuGet configuration instructions to README for Windows builds Co-authored-by: dkocher <71733+dkocher@users.noreply.github.com> --- README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/README.md b/README.md index 2206048659d..a0a4f03fdd5 100644 --- a/README.md +++ b/README.md @@ -116,6 +116,19 @@ Make sure that `MSBuild`, `mvn`, `ant` and `java` are on your `PATH`-environment Additionally include the latest Windows Sdk-binary folder in your `PATH`-environment variable: * `%ProgramFiles(x86)%\Windows Kits\10\bin\10.0..0\x64` +#### NuGet Configuration + +To build on Windows, you need to configure NuGet with credentials to access GitHub Package Registry sources. Create a GitHub [personal access token (classic)](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry) with at least `read:packages` permissions. + +Then, in the Cyberduck repository root directory, run the following commands in Terminal (PowerShell or Command Prompt): + +```sh +dotnet nuget update source gh-ikvmnet -u "YourUsername" -p "YourPAT" +dotnet nuget update source gh-iterate-ch -u "YourUsername" -p "YourPAT" +``` + +Replace `YourUsername` with your GitHub username and `YourPAT` with your personal access token. + ## Building Run `mvn verify -DskipTests -DskipSign` to build without running any tests and skip codesign. Find build artifacts in