Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions CopyDatabase/CopyDatabase.csproj
Original file line number Diff line number Diff line change
Expand Up @@ -13,8 +13,8 @@
<PackageReference Include="CommunityToolkit.Common" Version="8.4.2" />
<PackageReference Include="CommunityToolkit.Mvvm" Version="8.4.2" />
<PackageReference Include="MahApps.Metro" Version="2.4.11" />
<PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="10.0.8" />
<PackageReference Include="Microsoft.Extensions.Logging" Version="10.0.8" />
<PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="10.0.10" />
<PackageReference Include="Microsoft.Extensions.Logging" Version="10.0.10" />
Comment on lines +16 to +17

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Regenerate ClickOnce artifacts with these package versions

In this repo the README directs users to install the current app from Publish/CopyDatabase.application, and the publishing instructions say to commit the generated Publish/ output after publishing; this bump updates only the project file, while the advertised ClickOnce manifest still points to CopyDatabase_1_0_0_17 and that deployment's deps file still lists Microsoft.Extensions.DependencyInjection and Microsoft.Extensions.Logging as 10.0.8. Anyone installing from the documented link will continue receiving the old assemblies, so the dependency update does not actually reach users until the ClickOnce artifacts are regenerated, signed, and committed.

Useful? React with 👍 / 👎.

</ItemGroup>

<ItemGroup>
Expand Down