Skip to content

Bump the dotnet group with 3 updates #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
HarryCordewener merged 3 commits into from
Sep 22, 2026
+16 −4
Merged

Bump the dotnet group with 3 updates #17

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
845cf71
Bump the dotnet group with 3 updates
dependabot[bot] Sep 21, 2026
d8a18d0
Answer Verify 33's maintenance-fee check with its OpenSource exemption
HarryCordewener Sep 22, 2026
45741df
Merge branch 'main' into dependabot/nuget/MarkupString.Tests/dotnet-4…
HarryCordewener Sep 22, 2026
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
14 changes: 13 additions & 1 deletion Directory.Build.props
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,19 @@
</PropertyGroup>

<!--
Package metadata that is identical across the shipping packages. Everything that
Verify 33 fails the build unless the consumer answers its maintenance-fee check. MarkupString is
open source and earns nothing, which is Verify's own OpenSource exemption. The exemption is
time-bounded, at most twelve months out, so this date has to be moved forward (or the answer
changed) before it passes — the build says so when it lapses. Verify's terms:
https://github.com/VerifyTests/Verify/blob/main/docs/maintenance-fee.md
-->
<PropertyGroup>
<Verify_SponsorshipExemption>OpenSource</Verify_SponsorshipExemption>
<Verify_SponsorshipExemptionUntil>2027-09</Verify_SponsorshipExemptionUntil>
</PropertyGroup>

<!--
Package metadata that is identical across the three shipping packages. Everything that
differs per package — PackageId, AssemblyName, Description, project references — stays in
the project file. Test and smoke projects set IsPackable=false, so these are inert there.
-->
Expand Down
6 changes: 3 additions & 3 deletions MarkupString.Tests/MarkupString.Tests.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,12 +8,12 @@
<NoWarn>TUnit0038;TUnitAssertions0002</NoWarn>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="CsCheck" Version="4.8.0" />
<PackageReference Include="TUnit" Version="1.66.27" />
<PackageReference Include="CsCheck" Version="4.9.1" />
<PackageReference Include="TUnit" Version="1.68.17" />
<!-- Verify.TUnit carries a floor on TUnit.Core. Bump the two together: if NuGet lifts
TUnit.Core past the TUnit.Engine this project asks for, the split versions fault at
startup with MissingFieldException rather than failing to restore. -->
<PackageReference Include="Verify.TUnit" Version="32.0.0" />
<PackageReference Include="Verify.TUnit" Version="33.1.1" />
</ItemGroup>
<ItemGroup>
<ProjectReference Include="..\MarkupString\MarkupString.csproj" />
Expand Down
Loading