Skip to content

fix(core): restore the samples to the floating version #371

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
Ank-KhoaHo merged 1 commit into from
Aug 24, 2026
Merged

fix(core): restore the samples to the floating version #371

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
18 changes: 1 addition & 17 deletions samples/Container/Container.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,23 +5,7 @@
</PropertyGroup>

<ItemGroup>
<!--
PINNED, TEMPORARILY, AND THIS MUST GO BACK TO "*" ONCE 0.36.1 IS PUBLISHED.

"*" is the deliberate canary: it resolves to the newest published stable release, so a sample
is the first thing to break when a release is wrong. On 2026-08-24 it did exactly its job -
0.36.0 shipped DocToolkit.dll alone, and these samples went from building to 36 compile
errors. See F11 / the hotfix PR.

But the canary firing also blocks the fix: release.yml builds this solution before it packs,
so with "*" resolving to the broken 0.36.0 there is no way to publish the version that
repairs it. Pinning to the last good release is the only way out that does not require
unlisting 0.36.0 first.

RESTORE THIS TO "*" the moment 0.36.1 is on nuget.org. A pinned sample is a disarmed canary,
and this repo has already lost that canary for weeks once by leaving a floor here.
-->
<PackageReference Include="Ank.DocToolkit" Version="0.35.0" />
<PackageReference Include="Ank.DocToolkit" Version="*" />
</ItemGroup>

</Project>
18 changes: 1 addition & 17 deletions samples/DocxImages/DocxImages.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,23 +5,7 @@
</PropertyGroup>

<ItemGroup>
<!--
PINNED, TEMPORARILY, AND THIS MUST GO BACK TO "*" ONCE 0.36.1 IS PUBLISHED.

"*" is the deliberate canary: it resolves to the newest published stable release, so a sample
is the first thing to break when a release is wrong. On 2026-08-24 it did exactly its job -
0.36.0 shipped DocToolkit.dll alone, and these samples went from building to 36 compile
errors. See F11 / the hotfix PR.

But the canary firing also blocks the fix: release.yml builds this solution before it packs,
so with "*" resolving to the broken 0.36.0 there is no way to publish the version that
repairs it. Pinning to the last good release is the only way out that does not require
unlisting 0.36.0 first.

RESTORE THIS TO "*" the moment 0.36.1 is on nuget.org. A pinned sample is a disarmed canary,
and this repo has already lost that canary for weeks once by leaving a floor here.
-->
<PackageReference Include="Ank.DocToolkit" Version="0.35.0" />
<PackageReference Include="Ank.DocToolkit" Version="*" />
</ItemGroup>

</Project>
18 changes: 1 addition & 17 deletions samples/DocxTemplating/DocxTemplating.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,23 +5,7 @@
</PropertyGroup>

<ItemGroup>
<!--
PINNED, TEMPORARILY, AND THIS MUST GO BACK TO "*" ONCE 0.36.1 IS PUBLISHED.

"*" is the deliberate canary: it resolves to the newest published stable release, so a sample
is the first thing to break when a release is wrong. On 2026-08-24 it did exactly its job -
0.36.0 shipped DocToolkit.dll alone, and these samples went from building to 36 compile
errors. See F11 / the hotfix PR.

But the canary firing also blocks the fix: release.yml builds this solution before it packs,
so with "*" resolving to the broken 0.36.0 there is no way to publish the version that
repairs it. Pinning to the last good release is the only way out that does not require
unlisting 0.36.0 first.

RESTORE THIS TO "*" the moment 0.36.1 is on nuget.org. A pinned sample is a disarmed canary,
and this repo has already lost that canary for weeks once by leaving a floor here.
-->
<PackageReference Include="Ank.DocToolkit" Version="0.35.0" />
<PackageReference Include="Ank.DocToolkit" Version="*" />
</ItemGroup>

</Project>
18 changes: 1 addition & 17 deletions samples/HtmlConversion/HtmlConversion.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,23 +5,7 @@
</PropertyGroup>

<ItemGroup>
<!--
PINNED, TEMPORARILY, AND THIS MUST GO BACK TO "*" ONCE 0.36.1 IS PUBLISHED.

"*" is the deliberate canary: it resolves to the newest published stable release, so a sample
is the first thing to break when a release is wrong. On 2026-08-24 it did exactly its job -
0.36.0 shipped DocToolkit.dll alone, and these samples went from building to 36 compile
errors. See F11 / the hotfix PR.

But the canary firing also blocks the fix: release.yml builds this solution before it packs,
so with "*" resolving to the broken 0.36.0 there is no way to publish the version that
repairs it. Pinning to the last good release is the only way out that does not require
unlisting 0.36.0 first.

RESTORE THIS TO "*" the moment 0.36.1 is on nuget.org. A pinned sample is a disarmed canary,
and this repo has already lost that canary for weeks once by leaving a floor here.
-->
<PackageReference Include="Ank.DocToolkit" Version="0.35.0" />
<PackageReference Include="Ank.DocToolkit" Version="*" />
</ItemGroup>

</Project>
18 changes: 1 addition & 17 deletions samples/LargeFileStreaming/LargeFileStreaming.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,23 +5,7 @@
</PropertyGroup>

<ItemGroup>
<!--
PINNED, TEMPORARILY, AND THIS MUST GO BACK TO "*" ONCE 0.36.1 IS PUBLISHED.

"*" is the deliberate canary: it resolves to the newest published stable release, so a sample
is the first thing to break when a release is wrong. On 2026-08-24 it did exactly its job -
0.36.0 shipped DocToolkit.dll alone, and these samples went from building to 36 compile
errors. See F11 / the hotfix PR.

But the canary firing also blocks the fix: release.yml builds this solution before it packs,
so with "*" resolving to the broken 0.36.0 there is no way to publish the version that
repairs it. Pinning to the last good release is the only way out that does not require
unlisting 0.36.0 first.

RESTORE THIS TO "*" the moment 0.36.1 is on nuget.org. A pinned sample is a disarmed canary,
and this repo has already lost that canary for weeks once by leaving a floor here.
-->
<PackageReference Include="Ank.DocToolkit" Version="0.35.0" />
<PackageReference Include="Ank.DocToolkit" Version="*" />
</ItemGroup>

</Project>
18 changes: 1 addition & 17 deletions samples/LegacyDoc/LegacyDoc.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,23 +5,7 @@
</PropertyGroup>

<ItemGroup>
<!--
PINNED, TEMPORARILY, AND THIS MUST GO BACK TO "*" ONCE 0.36.1 IS PUBLISHED.

"*" is the deliberate canary: it resolves to the newest published stable release, so a sample
is the first thing to break when a release is wrong. On 2026-08-24 it did exactly its job -
0.36.0 shipped DocToolkit.dll alone, and these samples went from building to 36 compile
errors. See F11 / the hotfix PR.

But the canary firing also blocks the fix: release.yml builds this solution before it packs,
so with "*" resolving to the broken 0.36.0 there is no way to publish the version that
repairs it. Pinning to the last good release is the only way out that does not require
unlisting 0.36.0 first.

RESTORE THIS TO "*" the moment 0.36.1 is on nuget.org. A pinned sample is a disarmed canary,
and this repo has already lost that canary for weeks once by leaving a floor here.
-->
<PackageReference Include="Ank.DocToolkit" Version="0.35.0" />
<PackageReference Include="Ank.DocToolkit" Version="*" />
</ItemGroup>

<!--
Expand Down
18 changes: 1 addition & 17 deletions samples/MarkdownConversion/MarkdownConversion.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,23 +5,7 @@
</PropertyGroup>

<ItemGroup>
<!--
PINNED, TEMPORARILY, AND THIS MUST GO BACK TO "*" ONCE 0.36.1 IS PUBLISHED.

"*" is the deliberate canary: it resolves to the newest published stable release, so a sample
is the first thing to break when a release is wrong. On 2026-08-24 it did exactly its job -
0.36.0 shipped DocToolkit.dll alone, and these samples went from building to 36 compile
errors. See F11 / the hotfix PR.

But the canary firing also blocks the fix: release.yml builds this solution before it packs,
so with "*" resolving to the broken 0.36.0 there is no way to publish the version that
repairs it. Pinning to the last good release is the only way out that does not require
unlisting 0.36.0 first.

RESTORE THIS TO "*" the moment 0.36.1 is on nuget.org. A pinned sample is a disarmed canary,
and this repo has already lost that canary for weeks once by leaving a floor here.
-->
<PackageReference Include="Ank.DocToolkit" Version="0.35.0" />
<PackageReference Include="Ank.DocToolkit" Version="*" />
</ItemGroup>

</Project>
18 changes: 1 addition & 17 deletions samples/PdfUtilities/PdfUtilities.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,23 +7,7 @@
<!-- Version="*" is explained in samples/README.md. PdfEditor arrived in 0.15.0, so this project
could not exist until that release was published - which is the lag working, not a gap. -->
<ItemGroup>
<!--
PINNED, TEMPORARILY, AND THIS MUST GO BACK TO "*" ONCE 0.36.1 IS PUBLISHED.

"*" is the deliberate canary: it resolves to the newest published stable release, so a sample
is the first thing to break when a release is wrong. On 2026-08-24 it did exactly its job -
0.36.0 shipped DocToolkit.dll alone, and these samples went from building to 36 compile
errors. See F11 / the hotfix PR.

But the canary firing also blocks the fix: release.yml builds this solution before it packs,
so with "*" resolving to the broken 0.36.0 there is no way to publish the version that
repairs it. Pinning to the last good release is the only way out that does not require
unlisting 0.36.0 first.

RESTORE THIS TO "*" the moment 0.36.1 is on nuget.org. A pinned sample is a disarmed canary,
and this repo has already lost that canary for weeks once by leaving a floor here.
-->
<PackageReference Include="Ank.DocToolkit" Version="0.35.0" />
<PackageReference Include="Ank.DocToolkit" Version="*" />
</ItemGroup>

</Project>
18 changes: 1 addition & 17 deletions samples/Presentations/Presentations.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,23 +5,7 @@
</PropertyGroup>

<ItemGroup>
<!--
PINNED, TEMPORARILY, AND THIS MUST GO BACK TO "*" ONCE 0.36.1 IS PUBLISHED.

"*" is the deliberate canary: it resolves to the newest published stable release, so a sample
is the first thing to break when a release is wrong. On 2026-08-24 it did exactly its job -
0.36.0 shipped DocToolkit.dll alone, and these samples went from building to 36 compile
errors. See F11 / the hotfix PR.

But the canary firing also blocks the fix: release.yml builds this solution before it packs,
so with "*" resolving to the broken 0.36.0 there is no way to publish the version that
repairs it. Pinning to the last good release is the only way out that does not require
unlisting 0.36.0 first.

RESTORE THIS TO "*" the moment 0.36.1 is on nuget.org. A pinned sample is a disarmed canary,
and this repo has already lost that canary for weeks once by leaving a floor here.
-->
<PackageReference Include="Ank.DocToolkit" Version="0.35.0" />
<PackageReference Include="Ank.DocToolkit" Version="*" />
</ItemGroup>

<!--
Expand Down
18 changes: 1 addition & 17 deletions samples/Protection/Protection.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,23 +5,7 @@
</PropertyGroup>

<ItemGroup>
<!--
PINNED, TEMPORARILY, AND THIS MUST GO BACK TO "*" ONCE 0.36.1 IS PUBLISHED.

"*" is the deliberate canary: it resolves to the newest published stable release, so a sample
is the first thing to break when a release is wrong. On 2026-08-24 it did exactly its job -
0.36.0 shipped DocToolkit.dll alone, and these samples went from building to 36 compile
errors. See F11 / the hotfix PR.

But the canary firing also blocks the fix: release.yml builds this solution before it packs,
so with "*" resolving to the broken 0.36.0 there is no way to publish the version that
repairs it. Pinning to the last good release is the only way out that does not require
unlisting 0.36.0 first.

RESTORE THIS TO "*" the moment 0.36.1 is on nuget.org. A pinned sample is a disarmed canary,
and this repo has already lost that canary for weeks once by leaving a floor here.
-->
<PackageReference Include="Ank.DocToolkit" Version="0.35.0" />
<PackageReference Include="Ank.DocToolkit" Version="*" />
</ItemGroup>

<!--
Expand Down
18 changes: 1 addition & 17 deletions samples/Spreadsheets/Spreadsheets.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,23 +5,7 @@
</PropertyGroup>

<ItemGroup>
<!--
PINNED, TEMPORARILY, AND THIS MUST GO BACK TO "*" ONCE 0.36.1 IS PUBLISHED.

"*" is the deliberate canary: it resolves to the newest published stable release, so a sample
is the first thing to break when a release is wrong. On 2026-08-24 it did exactly its job -
0.36.0 shipped DocToolkit.dll alone, and these samples went from building to 36 compile
errors. See F11 / the hotfix PR.

But the canary firing also blocks the fix: release.yml builds this solution before it packs,
so with "*" resolving to the broken 0.36.0 there is no way to publish the version that
repairs it. Pinning to the last good release is the only way out that does not require
unlisting 0.36.0 first.

RESTORE THIS TO "*" the moment 0.36.1 is on nuget.org. A pinned sample is a disarmed canary,
and this repo has already lost that canary for weeks once by leaving a floor here.
-->
<PackageReference Include="Ank.DocToolkit" Version="0.35.0" />
<PackageReference Include="Ank.DocToolkit" Version="*" />
</ItemGroup>

</Project>
18 changes: 1 addition & 17 deletions samples/Telemetry/Telemetry.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,23 +8,7 @@
this project could not exist until that release was published - which is the lag working,
not a gap. -->
<ItemGroup>
<!--
PINNED, TEMPORARILY, AND THIS MUST GO BACK TO "*" ONCE 0.36.1 IS PUBLISHED.

"*" is the deliberate canary: it resolves to the newest published stable release, so a sample
is the first thing to break when a release is wrong. On 2026-08-24 it did exactly its job -
0.36.0 shipped DocToolkit.dll alone, and these samples went from building to 36 compile
errors. See F11 / the hotfix PR.

But the canary firing also blocks the fix: release.yml builds this solution before it packs,
so with "*" resolving to the broken 0.36.0 there is no way to publish the version that
repairs it. Pinning to the last good release is the only way out that does not require
unlisting 0.36.0 first.

RESTORE THIS TO "*" the moment 0.36.1 is on nuget.org. A pinned sample is a disarmed canary,
and this repo has already lost that canary for weeks once by leaving a floor here.
-->
<PackageReference Include="Ank.DocToolkit" Version="0.35.0" />
<PackageReference Include="Ank.DocToolkit" Version="*" />
</ItemGroup>

</Project>
Loading