From 96dd1761217cffafb558bce3c4049d0f74b71769 Mon Sep 17 00:00:00 2001 From: Jaap-Jan de Wit | DodoTech Date: Sat, 3 Oct 2026 19:44:25 +0200 Subject: [PATCH] CI: move vpk and Velopack to 1.2.161, whose Gitea upload survives the forge's new release responses The desktop nightly has failed on every push to main since 2 October, at 'publish the nightly release'. vpk 1.2.0 creates the draft release and then reads release.Assets from the forge's answer, which the upgraded server (28.0.0) no longer fills in for a new release, so it threw a NullReferenceException at GiteaRepository.cs:136. The step deletes the previous nightly-desktop release before it uploads, so desktop clients have had no nightly to update from since. 1.2.161 reads the assets null-safely. The library moves with the tool, since Velopack expects the two to match. Every vpk option the workflow and the release scripts pass is present in 1.2.161; the only renamed ones are two MSI options nothing here uses. --- .config/dotnet-tools.json | 2 +- Directory.Packages.props | 2 +- src/DodoSSH.Client.App/packages.lock.json | 6 +++--- tests/DodoSSH.Client.App.Layout.Tests/packages.lock.json | 8 ++++---- tests/DodoSSH.Client.App.Tests/packages.lock.json | 8 ++++---- 5 files changed, 13 insertions(+), 13 deletions(-) diff --git a/.config/dotnet-tools.json b/.config/dotnet-tools.json index f6dc1ff..7ec6454 100644 --- a/.config/dotnet-tools.json +++ b/.config/dotnet-tools.json @@ -10,7 +10,7 @@ "rollForward": false }, "vpk": { - "version": "1.2.0", + "version": "1.2.161", "commands": [ "vpk" ], diff --git a/Directory.Packages.props b/Directory.Packages.props index 8d8fd23..4195a2c 100644 --- a/Directory.Packages.props +++ b/Directory.Packages.props @@ -172,7 +172,7 @@ constant rather than a setting: an operator who could answer the update check could pin a chosen user to a known-vulnerable build. See docs/adr/0013-desktop-distribution-and-updates.md. --> - +